MGFoster wrote:
Same thing happened to me today: Access 2002 & PostgreSQL 8.0.1 on
Windows XP, using ODBC DSN. When you find an answer I'd sure like to
know what it is.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
When I got the error
ODBC --call failed.
blank (#110)
I had started the PostgreSQL server w/ a Windows Admin user account.
PostgreSQL won't allow you to connect to the server when an Windows
Admin account starts the service.
Solution (Windows XP Professional & Access XP):
Make sure your machine is not connected to the Internet.
Create a Windows, non-admin user account, log into Windows on that
account & start the PostgreSQL server. Create a DB & table in
PostgreSQL using the pgAdmin program. Create a DSN to that DB. Open
Access & link to that table using the DSN you just created. It should
work.
Log off the non-admin account & switch to a Windows Admin account. Open
another Access mdb file, different from the one opened above, and create
a link to the table in PostgreSQL. That should also work.
When my machine was connected to the Internet & I started the PostgreSQL
service Access couldn't open the linked table. Error:
Could not connect to the server;
Could not connect to the remote socket. (#101)
I disconnected from the Internet & started the service again. I could
open the linked table. I stopped the service, reconnected to the
Internet, started the service & then I COULD connect to the table!?
After a few minutes connected to the Internet when I tried to open the
table again I got the same message! I don't know what's going on.
There were other problems w/ changing permissions on the DB (to GRANT
ALL), which caused the successfully linked tables to show #Deleted in
the rows!?
Sigh... Back to testing....
--
MGFoster:::mgf0 0 <at> earthlink <decimal-point> net
Oakland, CA (USA)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBQjiY9YechKq OuFEgEQI3SQCfQQ zWC8ocUr1AdAlf6 Z9Nq+OhvcYAn2jg
iQIfDv3JCnGHxju g/BWHMgMp
=VS6h
-----END PGP SIGNATURE-----