Report based on Stored procedure doesn't work on client machine 1

[lechuck]

I have a report created with RDC in VB6 with Crystal Reports 8.5.
The report gets data from a stored procedure (MS SQL2000).

All works fine from my development machine, the report publish the data and can be viewd in the crystal viewer component.
But when I put my application on a client machine and test the report I get no result. All I get is a blank CRViewer and a messagebox with "SQL Server Error".

I've tested the following:
Installed MS SQL2000 and the database on the client machine.
I've tried to run my app from my development machine and connect to the new database, works fine. But not from the client machine.

I've started the SQL profiler to monitor the events that takes place on the database I've get the folowing result
when I run the report from the development computer:
RDC:Completed | exec [MyDB]..sp_procedure_params_rowset N'sp_getInnehData', 1, NULL, NULL
RDC:Completed | exec sp_getInnehData;1 86

the result when running the report from the client machine is only:
RDC:Completed | exec sp_procedure_params_rowset N'sp_getInnehData', 1, N'', NULL

It seems like the execution from the client machine can connect to the database, but somehow it can't complete the task to get the result from the procedure.

There are no problems from the client machine with reports that get's data from databas tables, with simple SELECT yada FROM yadayada...)
Is there any specific crystal dll that i need to install on the klient machine to get reports based on stored procedure to work?

Regards
Lechuck

 

[vidru]

I would start by checking permissions on the stored procedure.

-dave

 

[lechuck]

Permissions are ok, public does have execute rights.
Ive tried using the same account from both machines.

/lechuck

 

[vidru]

What connectivity type are you using (ODBC, OLEDB, Native, etc.)? There's a KB article about a bug with OLEDB and CR 8.5 in regards to stripping the DBName.dbo off of a stored proc:

http://support.businessobjects.com/library/kbase/articles/c2009878.asp

-dave

 

[lechuck]

I'm using OLEDB, the KB article you refere to seems to be the problem!
Thanks vidru, last question...
A customer has this application installed, and when they get te new version of the app with the new report, do you think that I only have to distribute the new P2soledb.dll or do I have to distribute the entire service pack?

 

[lechuck]

Hmm probably isn't only the p2soledb.dll file enough..

 

[vidru]

Good question. You can try reading the documentation (if there is any) in the service pack/hotfix to see if they list that specific issue, and what .dlls were affected. They typically do a pretty good job of documenting what gets fixed.

Of course, the optimal way to find out would be to test locally, i.e. duplicate the error on a test machine, then just replace P2soledb.dll with the updated version.

-dave

 

[lechuck]

I did a little work around, so I didn't need to install the service pack on the client machine

myReport.Database.Tables(1).Location = sDatabase & ".dbo." & myReport.Database.Tables(1).Location

Thanks for your help vidru!