Ok it seems I have the older version 9.0.2720 and they have the latest version service pack 9.0.3821 SR-1 BUT only one of the users has the same version that I do and STILL the sp do not work? Do you happen to know why?

Thanks
slypunk

Try creating a new adp from a pc that has the latest version. See if that works on the user pc and yours.





Sal

Thank you very much for your help I will try that and let you know how it goes.

slypunk

It's been a while since I sent this message but I just finished updated the users with the latest service pack version. The version fyi is Microsoft Access 2000 (9.0.3821 SR-1) I then checked each machine and came across two problems. On one of the pcs the forms and reports whose record source is a stored procedure still does not work. In other words when I want to view a form or report and I click on it, it will not open. On other pcs it gives me the following error when I try to open a report or form "Run-time error '2750': The operation on the No such interface supported object failed. I have been struggling with this for months as you can see. Any help at all I would greatly appreciate. Thank you :)

slypunk

I cannot figure out my problem it's very difficult to determine what the actual problem is to begin with. The ODBC connection looks fine to me and the service paks are updated. I am extremely stuck on this problem and I need for users to start utlizing these dbs. This is a project I started at works a couple of months ago. I placed the dbs on the server where every user can access BUT it is not working appropriately. I GREATLY NEED HELP ON THIS!!! Thanks :S

slypunk

I dono- but it seems that getting support for an access problem in a SQL forum isn't going to get you as much help as you need... Perhaps you should post the question in a forum focused on access? I don't even understand your problem to help you with it. What's the COMPLETE arcitecture.

I'd suspect that the lock placed on the database by the user over the network (or another user in the database at the same time) is somehow preventing the procedure from running properly. But that's a guess. It could be user rights for the SP.

And I am stumped as to why anyone would use a ODBC connection - rather than using ADO.





Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

Hello
Could you tell me which version of Access/Office are you using (if you have been unable to find a solution till now) and with any service pack or not. I had the same problem and was able to resolve it by reading your forum session.
Regards
Azam

You can do is add "dbo". in front of the store procedures name in your users form. like this dbo.storeproceduresname. Using access ADP as your front end application and SQL as the back end you must either give permission to users to execute the stored procedure or let them run it under dbo security context.

I'v had the same problem.
Install the SQl Server clients tools on every machine which uses the database and make a connection to the SQL Server with the username of the dbo.

For the most part it is a fast way to get a report populated in an Access ADP, but you are right. I do not use that method. ADO is a better alternative. This was an issue with user rights and not using the fully qualified name "dbo.StoredProcedure1".

Access 2000 had this problem. It was later fixed with a service release. ADPs were new to Access 2k and this was one of the main problems with it.

A stored procedure can not lock the way that a table can lock. also an ADP is not the same as an MDB. ADPs are more of a front end to SQL Server allowing a user to create stored procedures with MS Access.



Sal