Ok this is a bit strange so please bear with me.
CR version: 8.5
VB version: 6.0 wSP5
I've created a report inside my vb app by using the RDC.
The data is coming from a stored procedure in SQL Server (8.0) so I initially created the report by specifying 'Microsoft SQL Server' as my database driver.
The report worked fine on my development machines, both of which have SQL Server running on them. When I go to run the report on the actual user machines I get the 'physical database not found' that indicates that the required database dll is not present. This I have confirmed by installing the CR client on the user's machine and opening the report (.rpt file exported from the original RDC report). When I try to open it I get the message that it can't find the DLL and it says it's missing pdssql.dll.
Fine. So I search my development machines and even they don't have the pdssql.dll so that's driving me crazy but I figure I can just change my database driver to something else.
On the client I open up the report, change the database driver to OLEDB for SQL and the report works great. This seems like the best solution so I go back to my development machine and try to change the database driver to OLEDB and it's not an option.
So my questions are as follows:
1. If you know where I can find pdssql.dll please let me know since this is the easiest solution.
2. How to I get OLEDB to show up as one of my database driver choices in CR on my development machine? If I create the report using ADO I can't get to my stored procedure for some reason.
3. Anything else I can try? This is driving me nuts!
Thanks in advance for any help you can provide.




Reply With Quote