CR9: failed to open rowset error after changing record selection formula

[Former Member]

Hello,

I created a simple report that displays the cost of implants in surgeries performed in a specific date range. The records are grouped by Facility and Procedure Group.

When I change the selection formula to only include a specific surgeon, CR9 throws the errors "Failed to open a rowset" and "Not supported. Details: Error Code: 0x800a0bcd." The error doesn't occur if I remove the groups.

Has anyone had the same problem?

Thanks,

Teddy

[former_member183750 · Accepted solution]

need more information:

1) What language are you developing in?

2) What database are you connecting to?

3) What is your database connection type (ODBC, OLE DB, etc.)?

4) Does the report run as expected in the CR designer?

5) Have you applied any updates to your version of CR?

6) Is this happening on your development system, or once that app is deployed?

7) Is this a web or a win app?

😎 What is the exact version of CR used (9.1, 9.2)?

Ludek

[Former Member · Accepted solution]

Ludek,

1) The report itself fails. I'm not developing in any language.

2) I'm connected to SQL Server 2000.

3) The connection type is OLE DB.

4) The report fails in the CR designer.

5) No updates to CR.

6) The error happens in both environments.

7) The reports will go into a win app, but it's not even running as a stand-alone report.

😎 CR 9.2.2.634

Teddy

[former_member183750 · Accepted solution]

ahh, oops. This forum is dedicated to topics related to legacy SDKs, including the Report Designer Component (RDC), OCX, VCL, and Crystal Reports Print Engine (CRPE).

I'll see if I have the rights to transfer the post to the Crystal Reports Design forum:

Ludek

[former_member292966 · Accepted solution]

Hi Teddy,

Seeing as it works if you remove the grouping, what fields are you grouping on? If you were to remove one group at a time, hopefully that will pinpoint where the problem is.

It's possible one of the fields you are grouping on has been changed in the database. If you Verify the database, see if that fixes the problem.

A change in datatypes will cause this problem. Also if the size of a String field has been increased beyond 256 characters. This forces this version of Crystal to see that field as a Memo field now and cannot be used to group or in formulas.

Good luck,

Brian

[Former Member · Accepted solution]

Hi Brian,

Thanks for the quick response.

I'm grouping on facility (string(10)) and procedure group (string(25)). The selection formula only works when both groups are removed.

I tried to verify the database several times, but got the same result. I'm connecting to a stored procedure and the data type hasn't changed.

I don't know if this is important, but it's strange to me. After the report fails, the parameter order changes and I'm unable to make it revert to the original order.

Teddy

[former_member292966 · Accepted solution]

Hi Teddy,

As a test, can you run the stored procedure in SQL Server and populate a table? I'm wondering if one of the fields you are grouping on is returning bad data.

I'm not sure if the issue with the parameters is a symptom or a side-effect of the problem. I'd almost guess it's a side-effect.

If you open the report in Crystal and go to File | Report Options and turn on Convert Null Values to Default and turn off Use Indexes for Speed. Now run it again, see if that fixes it.

Good luck,

Brian

[Former Member · Accepted solution]

Brian,

That did it the trick. There were no null values on the table. It was the Use Indexes for Speed option that was causing the error. Do you know what this option is for?

Thank you so much. I was getting stressed out over this.

Teddy