2950 error - Access 2007 ADP connecting to SQL 2005

[Guest]

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:
http://support.microsoft.com/kb/931407

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
display.

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.

Thanks.

 

[aaron.kempf]

you need to give more information

is this the same database?

do they have SQL permissions?

what is the err.description for error # 2950

 

[Guest]

Unfortunately I can't help except to say I have the same problem. I have
adjusted the form insert Microsoft suggests to showing if the ADP is trusted,
and it does come up as true. I can run all the stored procedures
individually, and they run perfectly fine. I've recreated the macro instead
of using the one we built in Access 2003, and it still fails with the 2950
error. It happens if I just put one procedure in that I know works
individually.

It cannot be a permission issue, I've setup an account with unlimited rights
to everything and it still occurs. Plus of course, the exact same ADP works
perfectly in 2003 for the same user.

I see several people like you with the problem in newsgroups, but I've yet
to see an answer. We have set aside one machine using 2003 just to be able
to run these macros, but that isn't a good answer.

I just am adding hoping that if more people have this problem and post about
it somehow we'll notice something (or perhaps someone who knows much more
about it than I do will notice something). There is no error description,
it's just a popup box that lists the macro name, action name condition,
arguments, and error number (which is 2950).

 

[Guest]

I finally found a work-around. I moved all the Macro code to in-line code.
That works. So you put in DoCmd.OpenStoredProcedure and DoCmd.RunSQL etc in
the event of the button. It was manual and boring... but got it out of the
way once and for all. Now the Access 2007 ADP works against the SQL 2005.

Hope this helps.

 

[Marco De Laet]

Also I have the same problem with the 2950 error message. Indeed one could change all its macro's to inline-code. But how do we handle this with the AutoExec in which I have only 1 command: "callProcedure ng_AutoExec". But even then it blocks and shows the 2950 error.

Any suggestion would be more than welcome.

Marco De Laet

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

 

[Guest]

Under Trusted Locations: have you tried enabling "subfolder of this location
is also trusted"?