469,344 Members | 5,505 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,344 developers. It's quick & easy.

ODBC--call failed error when trying to view a report

7
I am trying to view my reports based on a linked table database. However both the reports and the queries they're based on give me a "odbc--call failed" error. When I click on help it cites error 3146 and suggests that either the data source is on a network drive or that I am not connected to the network. I am not sure what either means but I am able to view the linked tables and access the database through data sources (ODBC) in administrative tools.

I am running a linked table database on Access 2000 on a Windows XP machine.

Any suggestions would be most appreciated.
Sep 4 '07 #1
5 6436
puppydogbuddy
1,923 Expert 1GB
I am trying to view my reports based on a linked table database. However both the reports and the queries they're based on give me a "odbc--call failed" error. When I click on help it cites error 3146 and suggests that either the data source is on a network drive or that I am not connected to the network. I am not sure what either means but I am able to view the linked tables and access the database through data sources (ODBC) in administrative tools.

I am running a linked table database on Access 2000 on a Windows XP machine.

Any suggestions would be most appreciated.
If you are trying to connect Access to a back end server via an ODBC connection, I would check with server db administrator to see if you have the proper security permissions to do so.

If that is not the answer, then I would verify that your ODBC driver you are using is not outdated.
Sep 4 '07 #2
kchang
7
If you are trying to connect Access to a back end server via an ODBC connection, I would check with server db administrator to see if you have the proper security permissions to do so.

If that is not the answer, then I would verify that your ODBC driver you are using is not outdated.
Checked the drivers and they appear to be the latest ones. I would like to think that I have the permissions to connect to the server via an ODBC connection. Like I said I can view the linked tables and connect to the server via a data link. Would having to login to the SQL Server using a password affect the reports and queries on Microsoft Access?
Sep 6 '07 #3
puppydogbuddy
1,923 Expert 1GB
Checked the drivers and they appear to be the latest ones. I would like to think that I have the permissions to connect to the server via an ODBC connection. Like I said I can view the linked tables and connect to the server via a data link. Would having to login to the SQL Server using a password affect the reports and queries on Microsoft Access?
Yes. The reports use the queries as the data source. The queries, in turn, access data from the tables in the Back End. Therefore, you must have a logon password with the proper permissions to connect via ODBC. See this link regarding the logon process.

http://support.microsoft.com/kb/q245587/

As stated in the article: In Microsoft Access, when you first link (attach) an external table using an ODBC driver, you have the option to store the User ID and password for the table locally..........(this means also that you must have a login ID and password with the proper permissions).
Sep 6 '07 #4
kchang
7
Yes. The reports use the queries as the data source. The queries, in turn, access data from the tables in the Back End. Therefore, you must have a logon password with the proper permissions to connect via ODBC. See this link regarding the logon process.

http://support.microsoft.com/kb/q245587/

As stated in the article: In Microsoft Access, when you first link (attach) an external table using an ODBC driver, you have the option to store the User ID and password for the table locally..........(this means also that you must have a login ID and password with the proper permissions).
I checked out the link and tried relinking my tables with the "Save Password" box checked, but I'm still receiving the error. I also looked at the third option listed: pre-authenticating the login, but I'm not entirely sure how to go about doing that as I am not very familiar with vb.
Sep 6 '07 #5
puppydogbuddy
1,923 Expert 1GB
I checked out the link and tried relinking my tables with the "Save Password" box checked, but I'm still receiving the error. I also looked at the third option listed: pre-authenticating the login, but I'm not entirely sure how to go about doing that as I am not very familiar with vb.
Does your password have permissions to access the back end tables via ODBC?

The link I gave you has sample code for pre-authenticating the login. Did you see it? As instructed, place the code behind a button and execute it by clicking the button dring the login, Replace the sample's parameters in the code with yours, where applicable. If you don't know how to do this, you need to talk to the dba for your server machine.
Sep 7 '07 #6

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

1 post views Thread by Jeff Thur | last post: by
2 posts views Thread by ticars | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
1 post views Thread by Marylou17 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.