ODBC--call failed.

[R. Wing]

I have a ms access 2000 database, at a client site, that I use to connect to
and extract data from an oracle 10 server. The queries and reports in this
data base were working fine until recently when I started getting the
"ODBC--call failed" message without any additional information. If I try to
link in a new table I get the following message however: ODBC--call failed.
[Microsoft][ODBC driver for Oracle][Orace](#0)
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed IM006 0
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (#0)

Can someone say definitvely what the problem is from the message? I've
moved the database to other workstations in this office and am able to run my
queries and reports just fine so the problem is with my workstation and not
the application.

Thanks in advance.

 

[Matthias Klaey]

I have a ms access 2000 database, at a client site, that I use to connect to
and extract data from an oracle 10 server. The queries and reports in this
data base were working fine until recently when I started getting the
"ODBC--call failed" message without any additional information. If I try to
link in a new table I get the following message however: ODBC--call failed.
[Microsoft][ODBC driver for Oracle][Orace](#0)
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed IM006 0
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (#0)

Can someone say definitvely what the problem is from the message? I've
moved the database to other workstations in this office and am able to run my
queries and reports just fine so the problem is with my workstation and not
the application.

Thanks in advance.

To debug ODBC errors, run something llike the following in yout error
handler:

For i = 0 To Errors.Count -1
Debug.Print Errors(i).Number, Errors(i).Description
Next

The lowest-numbered error (i.e., error(0)) is closest to the source of
the error and usually gives the best information about the actual
cause of the error.

HTH
Matthias Kläy

 

[R. Wing]

Thanks Matthias, this is a start. I know you can print the error
descriptions in code but am I suppost to integrate your code into the process
to trap the error as it happens? Here are my results from the Immediate
window:
?Errors.Count
0
?Errors(0).Description
Item not found in this collection.

Another proglem at this site is that they have problems keeping ms access
help working on the individual workstations. When acces says that help 'is
broke' and do I want to fix it, I indicate yes but it always fails - can't
locate the proper files. This may be reoccuring and that could be why I'm
getting the above error response. I'll get them to make sure my help is
working and try again. Thanks



--
R. Wing

I have a ms access 2000 database, at a client site, that I use to connect to
and extract data from an oracle 10 server. The queries and reports in this
data base were working fine until recently when I started getting the
"ODBC--call failed" message without any additional information. If I try to
link in a new table I get the following message however: ODBC--call failed.
[Microsoft][ODBC driver for Oracle][Orace](#0)
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed IM006 0
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (#0)

Can someone say definitvely what the problem is from the message? I've
moved the database to other workstations in this office and am able to run my
queries and reports just fine so the problem is with my workstation and not
the application.

Thanks in advance.

To debug ODBC errors, run something llike the following in yout error
handler:

For i = 0 To Errors.Count -1
Debug.Print Errors(i).Number, Errors(i).Description
Next

The lowest-numbered error (i.e., error(0)) is closest to the source of
the error and usually gives the best information about the actual
cause of the error.

HTH
Matthias Kläy