| Subject: | Re: How to configure Postgres ODBC Alias's for Multiple Difference Postgres Servers.
| | Date: | Mon, 18 May 2020 11:30:10 +1000
| | From: | Robert MacMillan <macfam@bigpond.net.au>
| | Newsgroups: | pnews.paradox-client_server
|
Well finally managed to fix it. There are many areas where the
documentation is really deficient and this is one of them.
The problem was that in the Alias in BDE the DNS was not specified -
blank. Right click on the Alias, fill in the database name, away laughing.
What was really frustrating is that filling in the ODBC parameters
allowed connection to test correctly. But the Alias did not work in
Paradox itself. The only way I found the solution was to compare the
parameters set in the AWS Aliases that did work to the local Alias that
didnt.
On 17/05/2020 5:57 PM, Robert MacMillan wrote:
> How does one go about having ODBC drivers and two different aliases that
> address different Postgres servers. In this case an AWS Server and
> secondly a local host?
>
|
