Geeks With Blogs


Add to Google

Tim Hibbard CEO for EnGraph software

One of our applications is an Access front end linked to a SQL backend. We link the tables and then all the database calls go against an ADODB connection.

This weekend, I was supposed to do a major upgrade for one of our clients. This upgrade was going to involve changing the database structure, so I had the DBA add drop and create table permissions to my SQL login.

Once the login permissions were changed, our application stopped working. The first place a data call was made, we would get a "could not find stored procedure" error.

I was able to get it back running by using CurrentProject.Connection as my connection and changing all my date deliminators from ' to #, but it didn't seem right.

This morning, I talked to the DBA and he had never heard of such a problem. He proceeded to remove the database access for our database for that login, and then re-added the database access and everything went back to normal.

Does anybody know if Access somehow caches SQL permissions? I'm not sure exactly went wrong, or how we fixed it. Somehow, by removing the database access for that login, it forced Access to update its permissions, or something...any ideas?

Posted on Monday, September 20, 2004 2:15 PM MS Office | Back to top

Comments on this post: Access linked to SQL problem

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Tim Hibbard | Powered by: