I have a MS Access 2000 front end application accessing a
MS SQL 7 database via ODBC. The application calls many
stored procedures in the database.
I have a new report and new stored procedure as the source
data for the report. Some users accessing the report via
a Windows 2000 Terminal Services session get a report
failure message indicating the stored procedure cannot be
found. When I access the report, either locally or via
Terminal Services, the report works fine.
I believe this is a rights issue since it works for me and
not for my remote users. I have granted full rights in
the database to the remote users for this stored procedure
but the result is the same.
Any Ideas? PLease help.

Who is the owner of the stored procedure? If it's not dbo,
try qualifying the call to the stored procedure with the
owner.

-Sue

On Mon, 18 Aug 2003 12:45:27 -0700, "Michael Wolfstone"
<Mike@Phxgroup.com> wrote:

>I have a MS Access 2000 front end application accessing a
>MS SQL 7 database via ODBC. The application calls many
>stored procedures in the database.
>I have a new report and new stored procedure as the source
>data for the report. Some users accessing the report via
>a Windows 2000 Terminal Services session get a report
>failure message indicating the stored procedure cannot be
>found. When I access the report, either locally or via
>Terminal Services, the report works fine.
>I believe this is a rights issue since it works for me and
>not for my remote users. I have granted full rights in
>the database to the remote users for this stored procedure
>but the result is the same.
>Any Ideas? PLease help.

Thanks, That did the job.



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!