Ms Access "ODBC Call Failed"

StampIT
StampIT used Ask the Experts™
on
In MS Access 2010 a user is encountering the message "ODBC Call Failed" when trying to preview a report. The data source for the report is a linked table from SQL Server 2008 R2. Another user using this same machine can execute the report preview without any issue. Guessing here that there is a SQL Server security issue with the user that is having difficulty. However I can find no obvious difference in the SQL Security between the two. The ODBC bridge is set up the same for both users as a Trusted Connection. Any idea what the issue might be here ? Not sure how to troubleshoot this. Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Dale FyeOwner, Dev-Soln LLC
Most Valuable Expert 2014
Top Expert 2010

Commented:
Have you looked at the permissions associated with both of the users in SQL Server.  Is there a chance that one of the users is assigned to a role or group that has permissions that the other user does not?

Author

Commented:
Yes i have compared the two at the SQL Server level and the database level and can find no difference.
Perhaps the DSN is set differently at user level..
Should you be charging more for IT Services?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
I have checked the ODBC setups for both users. Both are User DSN. Both are set up exactly the same. Thought maybe there was a way through SQL of determining why the second user ODBC call is failing.
Check in Access under options, there should be something connection timeout..

Author

Commented:
The only thing I see is "OLE/DDE timeout(sec)". It is set at 30. Is that what you are referring to ?

The users I refer to access the database with a runtime version of Access. They are accessing a copy of the original database. The "ODBC Call Failed" message is instantaneous. Thanks.
First try to recreate the DSN and install latest SQL native client, see if that helps.

If that doesnt help, you can try create a new user and see if that user also has this problem, if not then most likely something with this user got corrupt, and you should back up all their stuff and recreate it.
@StampIT,
Did you tried those suggestions?

Author

Commented:
No I have not been able to gain access to this users machine.  I have used SQL Native Client 10.0 with other users. Is that the version you are speaking of ?

Also I plan to try and connect to the SQL database using SQL authentication with this user

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial