Converting CR 8.5 to 9.0 report loses parameters???

[martingroup]

I am really struggling with an issue by which I have an 8.5 crystal report based on OLEDB driver. I open up the report in CR 9.0, connect to the database, verify database and the message states that "the database has changed, proceeding to fix up the report". I need to mention that the report uses a stored procedure.

This is all well and find unless the database has not really changed, but Crystal believe it does and after I click OK, Crystal proceeds to removes 2 of the 4 parameters from the report. The 2 parameters that are removed happen to be the actual stored procedure parameters themselves. Now I can seem to figure out what is going on and I cannot find any documentation or knowledge base articles that allude to a problem.

This is a SQL Server database.

Any help would be GREATLY appreciated.

 

[synapsevampire]

Interesting...

The fact that you get a database has been updated doesn't surprise me, the connectivity is probably different in CR 9, so when it verifies the database it finds some difference.

Try changing to the ODBC driver and see if that works.

Also try creating a new report using the SP using OLEDB and see if it only recognizes 2 of the parameters.

-k

 

[martingroup]

That was a good test, here are the results:

Created 4 different reports with same stored procedure and ran them with my VB6 app reference 9 RDC and viewer.

CR 9 (ODBC) - success

CR 9 (OLEDB) - success

CR 8.5 (ODBC) - Query Engine Error: '42502:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'DEV_EABC_P_ABC_AR.dbo.Proc(CP_ARGeneralLedgerDetailByBatchID_V100;1)'

CR 8.5 (OLEDB) - The table 'DEV_EABC_P_ABC_AR.dbo.Proc(CP_ARGeneralLedgerDetailByBatchID_V100;1)' could not be found.

Any other thoughts or direction?