Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
|
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old May 25th, 2004, 12:12 PM
Authorized User
 
Join Date: Jun 2003
Posts: 98
Thanks: 0
Thanked 0 Times in 0 Posts
Default stored procedures in ADP do not work on other comp

Hello I am working on an Access Project which works great on my computer. This database is placed on a server where users can access it. However I'm testing this on one of the user's computer and I noticed that the only forms and reports that are not working are the ones whose record source is a stored procedure. Am I doing something wrong? I cannot figure it out. Please if anyone can help me I'd greatly appreciate it. Please view this message I sent back in January.

Thanks

http://p2p.wrox.com/topic.asp?TOPIC_ID=8621

slypunk

slypunk
__________________
slypunk
 
Old May 25th, 2004, 01:14 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

have you give the users execute rights to the procedures? Are you using the dbo login as well to ensure that it is not a security issue?
It is more likely a security issue if it was not the SR issue.



Sal
 
Old May 25th, 2004, 01:27 PM
Authorized User
 
Join Date: Jun 2003
Posts: 98
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
quote:Originally posted by sal
 have you give the users execute rights to the procedures? Are you using the dbo login as well to ensure that it is not a security issue?
It is more likely a security issue if it was not the SR issue.



Sal
Do I check this by going to the stored procedure in the Enterprise Manager right click go to properties then permissions. If so, I have made sure that each user can execute these sps. What also confuses me is how some pcs receive the error of "The operation on the No such interface supported object failed." I do not know what other option is left. :(

slypunk
 
Old May 25th, 2004, 01:39 PM
Registered User
 
Join Date: May 2004
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I ran into the same distribution problem with stored procedures in combo boxes. I had to place dbo. in front of my stored procedres and it worked fine.

 
Old May 25th, 2004, 02:09 PM
Authorized User
 
Join Date: Jun 2003
Posts: 98
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
quote:Originally posted by Wango
 I ran into the same distribution problem with stored procedures in combo boxes. I had to place dbo. in front of my stored procedres and it worked fine.

dbo as in for example Employees; rename it to dboEmployees?

slypunk
 
Old May 25th, 2004, 02:39 PM
Registered User
 
Join Date: May 2004
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The original stored procdure(SP) name was prcCrsNum but when the adp front end was transferd to a user's PC the stored procdure name had dbo following it. So I went into the form and renamed the row source to dbo.prcCrsNum and it worked. I'm pretty new at this and it may be the wrong way but it works for now.

 
Old May 25th, 2004, 02:59 PM
Authorized User
 
Join Date: Jun 2003
Posts: 98
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
quote:Originally posted by Wango
 The original stored procdure(SP) name was prcCrsNum but when the adp front end was transferd to a user's PC the stored procdure name had dbo following it. So I went into the form and renamed the row source to dbo.prcCrsNum and it worked. I'm pretty new at this and it may be the wrong way but it works for now.

So am I but you know what I tried it and IT WORKED! Thank you very much. FINALLY this took me months to figure out and I got it to work! THank you

slypunk
 
Old May 25th, 2004, 04:03 PM
Authorized User
 
Join Date: Jun 2003
Posts: 98
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Ok question: It worked on one computer but not on the others? Does that mean I have to go to each machine individually to change the sps to dbo.?

slypunk
 
Old May 25th, 2004, 07:54 PM
Registered User
 
Join Date: May 2004
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I distrubute the access front end to each user. When i make changes i email them a new copy and have them delet the old one. This way they all have the same version.

 
Old May 25th, 2004, 08:49 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Create a table with the latest version number. then create another exe either in VB or even access. Put a splash form just for looks and when it loads have the form check the table to see if there is a newer file in the network. If the there is, do a filecopy. do a search on this forum for filecopy or copyfile, i gave someone else all the steps for this about 2 months ago.

Remember fully qualify your sql code with ownername.object name syntax.



Sal





Similar Threads
Thread Thread Starter Forum Replies Last Post
adp- stored query problem LeoTiger1 Access 0 June 13th, 2006 04:11 PM
Stored procedures won't work properly... eBilyboy SQL Server 2000 1 December 12th, 2005 11:25 AM
stored procedures in ADP do not work on other comp sherr8 SQL Server 2000 19 September 16th, 2004 10:29 AM
Use of "IF" in a ADP Stored Procedure Mickey123 Access 0 December 5th, 2003 01:53 AM
custom menus don't work with a shared adp Ash Access 3 August 12th, 2003 01:22 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.