CODEWITHSUNDEEP
sql-servervb6crystal-reports
user1451185
user1451185

Reputation:

Table [tablename] could not be found -2147189180

I have created a report using Crystal Reports XIr2 to report on information from a database for our application. It is a cross tab report, reporting on a variety of data returned from running a stored procedure.

A quick bit about the application that this report is run through - it is an application written in VB6, upon loading the application you are prompted for a username and password, which are configured on a SQL server as SQL logins, so when you log into the application you are authenticating against SQL server security.

The report is working absolutely fine in Crystal Reports, however I am experiencing some weird behaviour with this report when it is launched from within our application on a customer site. It works fine for all users with 'sa' level database access but gives the following error when run as any other user;

Error message

If I connect to the database server directly as a user that gets the above error within the application, running the stored procedures manually works without any errors.

If I give a user that is getting the error within our application 'sa' permissions on the SQL server, the error stops happening.

I have checked all related execute permissions for the stored procedure in question, but as stated if I connect to the SQL Server manually and execute the procedure, I do not get the error linked above.

If the user who is getting this error runs another report before this report, it works, however if they run a report after getting this error, all reports stop working and require an application restart.

Any ideas please?

Upvotes: 11

Views: 3337

Answers (2)

Yasker Yasker
Yasker Yasker

Reputation: 87

Granting execute permission doesn't always end there -- At times, you'll have to check the possible permission blocks of the objects within. When you say that you used the user's login to run the procedure manually, is it also for certain that the user's credentials are what you use to connect to the database?

Perhaps you can use a more universal sql login that the application will use -- this way you won't have to keep track of permissions for multiple users (just a suggestion! :) )

Upvotes: 0

Diego L Espiñeira
Diego L Espiñeira

Reputation: 156

I suggest you make sure the default schema of the user mapping for the database is set to dbo for the users reporting the issue. I also recommend using database roles for that.

Upvotes: 1

Related Questions