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

2950 error - Access 2007 ADP connecting to SQL 2005

P: 1
I am in the process of upgrading an old Access ADP/SQL 2000 App to Access
2007 ADP/SQL 2005.

There are a lot of buttons in the Access form which are calling Access
Macros, the Macros call Stored Procedures in the SQL database. This is
resulting in '2950 Error' for all the macros.

Here is Microsoft' answer for that error:
This issue occurs if the database is not trusted by Access 2007. By default, Access 2007 opens databases that are not trusted in Disabled mode. In Disabled mode, executable content is disabled.
*edit end*

I have followed all their steps. I have added the path of the .ADP as
Trusted in the 'Trust Center', I have kept the option of 'Display Info bar'
ON. I have said 'Run all Macros irrespective of whether they are signed' (I
know this is not recommended). I have checked the 'Trust all network
locations' box. I have also added a Form and added the AutoExecute macro
which should show that Form if the ADP is not trusted. This form does not

BUT, I continue to get the same 2950 error for all my Macros.

I am able to see all the SQL Server Tables and the Stored Procedures and
able to Modify them etc. Its executing the Sprocs that fails.

I have spent hours on this in the past few days searching the web for all
possible solutions and read up everything possible.

This is a bit frustrating. Each day is passing by without any progress.

Any help is much appreciated.
Jun 16 '07 #1
Share this Question
Share on Google+
1 Reply

Expert Mod 15k+
P: 31,494
I can't be a lot of help here I'm afraid, but from my reading of the MS article, you need to set your database (or your Access setup) to trust your link to the SQL Server 2005 database. I'm not sure how you'd go about doing this :(
Am I right in thinking all macros (or calls) work if they are NOT trying to run the SQL Server sProcs?
Jun 17 '07 #2

Post your reply

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