By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,639 Members | 2,276 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,639 IT Pros & Developers. It's quick & easy.

ODBC call failed

P: n/a
pu
Hi,

Could any one tell me what the following messages means please? And where
can I get the error messages with their descriptions?
===begin===
ODBC --call failed.
blank (#110)
===end===

I get this when I try to link a table into MsAccess from a postgresql
database.
If I link the table from my Linux6.2 Postgresql6.5 database, all is well.
If I link the table from my Linux9.0 Postgresql7.2 database, the above
happens.

===begin===
[root@linlee data]# rpm -a -q | grep postgres
postgresql-odbc-7.2.5-1
postgresql-contrib-7.3.2-3
postgresql-tcl-7.3.2-3
postgresql-libs-7.3.2-3
postgresql-7.3.2-3
postgresql-pl-7.3.2-3
postgresql-python-7.3.2-3
postgresql-jdbc-7.3.2-3
postgresql-test-7.3.2-3
postgresql72-libs-1-3
postgresql-server-7.3.2-3
postgresql-devel-7.3.2-3
===end===

Thanks in advance.
Leigh

cc to le*******@hotmail.com


Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
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.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

pu wrote:
Hi,

Could any one tell me what the following messages means please? And where
can I get the error messages with their descriptions?
===begin===
ODBC --call failed.
blank (#110)
===end===

I get this when I try to link a table into MsAccess from a postgresql
database.
If I link the table from my Linux6.2 Postgresql6.5 database, all is well.
If I link the table from my Linux9.0 Postgresql7.2 database, the above
happens.

Nov 13 '05 #2

P: n/a
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:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQjiY9YechKqOuFEgEQI3SQCfQQzWC8ocUr1AdAlf6Z9Nq+ OhvcYAn2jg
iQIfDv3JCnGHxjug/BWHMgMp
=VS6h
-----END PGP SIGNATURE-----
Nov 13 '05 #3

P: n/a
pu
I don't know whats going on either. Using Windows Xp and Access 2000 I can
log onto my Postgresql server on two linux 6.2 boxes that sport a Postgres
6.5.

When trying to connect to Linux 9.0 Postgres 7.5 setup, I get the #110 error
messages.

I get the same message connected to the net trying to log onto my ISP's
postgresql server (8.0). I don't know if they are running it under Linux or
what version of Linux.

But the error message Blank (#110) must mean something even if, I suspect,
it means unexpected error.

I wonder if there is a log I can look into that might shed some light?

Regards

Leigh

"MGFoster" <me@privacy.com> wrote in message
news:8V******************@newsread1.news.pas.earth link.net...
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.

Nov 13 '05 #4

P: n/a
MGFoster <me@privacy.com> wrote in
news:8V******************@newsread1.news.pas.earth link.net:
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!?


Isn't the #Deleted problem with ODBC links evidence of a lack of a
primary key or the lack of a time stamp?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.