|
|
 |
| 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 p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
|
 |

April 1st, 2004, 06:50 AM
|
|
Registered User
|
|
Join Date: Apr 2004
Location: Brighton, , United Kingdom.
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Record source ... does not exist
I'm having problems running reports in an Access 2000 ADP where the report's recordsource is a parameterized stored procedure (SQL 7/2000).
The parameters are being passed via the report's Input Parameters property, and are derived from a dialog box. This was working fine until the database was moved to a new server (backed-up and restored). Now I'm getting an error message "The record source '<<Stored Procedure Name>>' specified on this form or report does not exist" each time I try to run the report.
The ADP is connected to the correct Server/database. I've checked permissions, logins, 'dbo.' prefixes, etc. and can find nothing unusual. The stored procedure can be selected as the recordsource for the report in the ADP, and runs fine in SQL Query Analyser. The ADP has been opened and closed many times since moving the database, so it shouldn't be a problem with caching.
Any suggestions would be greatly appreciated!
|

April 1st, 2004, 09:40 AM
|
|
Friend of Wrox
|
|
Join Date: Nov 2003
Location: Lehigh Acres, FL, USA.
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
make sure you are specifying who has permission to run the store procedure. In the reports source. add dbo.<store procedure name>
|

April 1st, 2004, 10:03 AM
|
|
Registered User
|
|
Join Date: Apr 2004
Location: Brighton, , United Kingdom.
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Thanks for this.
Unfortunately, I've already checked this and the dbo. qualifier is already present.
It's only happening to sprocs that return a recordset to the .adp. All other sprocs that run from the .adp (e.g. to insert, update or delete records) are running without problems.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
 |