Crystal: Failed to open a rowset Details: 42000 The SELECT permission was denied on the object

Hello:

I have a database view that is used by a Crystal report.  I never got any issues, upon running the report (i.e. running the parameters of the report).

But, the end user got the following error message:  Crystal: Failed to open a rowset Details: 42000 The SELECT permission was denied on the object....

This is shown in the attachment called "why".  In the attachment called "why2", I took steps necessary to get rid of the error.  As soon as he rebooted his machine, he no longer got any errors.

Does this mean the steps that I took are the only means of getting rid of this error?

I, also, created a User DSN that "speaks" to only that database that the view is in.  Usually, I don't create User DSNs.  I create System DSNs.  But, the only DSN that showed up in Crystal when I created it was the User DSN.  Why is that?

Thanks!

I'm just trying to understand what eliminated the error.

TBSupport
why.docx
why2.docx
LVL 1
TBSupportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mlmccCommented:
For views on the database, you have to give the user permissions to run them.  That is the SELECT permission.

I believe the other issue of having to build a user dsn is related to the connection method.  You chose to use the native client which is installed on the client machine and is valid for that user.  Therefore the dsn must also be a user dsn.

mlmcc
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TBSupportAuthor Commented:
"I have a database view that is used by a Crystal report.  I never got any issues, upon running the report (i.e. running the parameters of the report).".....I can't even find myself in the list of SQL logins....how would I find myself in SQL?

"Does this mean the steps that I took are the only means of getting rid of this error?"....is modifying the properties of the view and granting "select" the cure for this?

"I, also, created a User DSN that "speaks" to only that database that the view is in.  Usually, I don't create User DSNs.  I create System DSNs.  But, the only DSN that showed up in Crystal when I created it was the User DSN.  Why is that?".....I never had to create a User DSN when I was creating the report--only a System DSN.  Why is the end user required to have a User DSN?

TBSupport
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Crystal Reports

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.