Unable to open rowset : Unknown error

[JohnEck]

I am running CR ver 9.0.2 on Win2k accessing SQL 2K through an ODBC connection.

I have been struggling with this error ever since I upgraded to CR 9.0. At first it was intermittant and just this week became a full blown meltdown. This was only occurring on reports that used SP calls to retrieve data. The difficult part was not all SPs had this problem. This week when it became a large problem I noticed it was only SPs that that deleted from than inserted into actual tables. I have been working on converting all the SPs to using temporary tables and this appears to be a workable solution. It has hit me with a performance penalty on some of the larger reports but at leas they work.

If you are getting this error and unable to track it try converting SPs to using temp tables.

 

[Chasidy]

I know how I have created that error in the past. In the Table Linking, if you have a chain of tables linked together, if you use one LEFT OUTER JOIN between two tables, the remaining tables on that "chain" also have to be LEFT OUTER JOINS regardless if you think it should be or not.
** This will generate error
a INNER JOIN b LEFT OUTER c INNER JOIN d

** This will not
a INNER JOIN b LEFT OUTER c LEFT OUTER d
I don't know if this helps your problem or not.

 

[JohnEck]

No my problem was with Store Procedures that used inserts into tables. If I use actual tables instead of temporary tables the SP crashes when called by Crystal even though it runs just fine in SQL Server.