Stored Procedure names and OLEDB

[kevstar]

I am trying to make crystal Reports connect to SQL server using OLEBD.

I have converted the database driver from ODBC to OLEDB, crystal tells me that it cannot find the stored procedures in SQL. This is because it suffixes all of the stored procedure names with ";1".

I am told that Crystal does this by default. If I delete this suffix in the "Set Location" page sometimes it works but the majority of times I get an error being produced in CRW32.exe It causes a fault and shuts down crystal.

Why does this happen and how do I remove the suffix on the stored procedure names?

Any help would be appreciated

Thanks again

Kev

 

[lyanch]

I have had this problem before. The ";1" that crystal adds has to do with SQL servers "grouping" of stored procedures. If you use the SQL server tools to actually create the SP I believe it automatically adds one, so crystal trys to as well.

As I recall, the solution for me was the following. I was using native not sure about how this work if you are using ODBC.

1. The obvious.. update the dll
2. Gave in to Crystal and fixed the SP's to have ;1.

That seemed to fix my problem.

Lisa

 

[kevstar]

Did that, now it works fine, thanks very much for your help

Kev