December 8, 2005 at 5:29 am
Hi,
For a while now I'm bundeling all of the small Access projects at work into 1 easy to use project. I'm using OLE DB to connect to the data that's located on SQL Server 2000.
All of the reports are based on views and SP's that are kept in 1 database in the server.
The data can be viewed by everyone that is in the Public group. (Basically everybody)
For one of my colleagues, who has a seperate account on the server but is also member of public, one of the reports is not working. I don't get any data on screen using his credentials.
I've checked the setting for his accounts securtiy settings and there is no difference to the setting of the public group.
The report in question uses an SP.
Does anyone know what may be the problem here?
December 8, 2005 at 7:51 am
Check whether the EXEC privilege on the SP is denied for the user.
December 8, 2005 at 7:56 am
peterhe,
The user has no specified grants or denies on any SP or view. The only role that has grants on the database is Public. He's part of that group so shouldn't that automatically grant him access?
P.S. thanks for the quick reply
December 8, 2005 at 8:20 am
Does the SP have dynamic TSQL code? Dynamic TSQL breaks owner chain and need to grant priviledge explicitly.
First of all, are you sure this is an security issue? run sql profiler to catche the SP call, run the call by "sa" account in query analyzer and see whether you can any results.
December 9, 2005 at 5:42 am
peterhe,
I've monitored the SP on several user accounts including the one that's not working. I tested the output using Query analyzer and the resultset I got was what it should be.
The only difference I found between "working" users and the one not working was the date setting at startup.
For the working users, the setting states "MDY", the not working states "DMY".
Does this affect my work knowing that the parameter send to the SP from Access id in fact a date?
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply