Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failed to Open Rowset Error

Status
Not open for further replies.

lkerr

Technical User
Mar 2, 2005
162
US
Hi, I'm using CR9 with ODBC connection to MS SQL (2003, I think). Here's my problem:

I have a report with three subreports - all with the same linking criterion. Last week, for reasons unknown to me, this report started failing without any particular reason.

The subreports are linked via the customerID and contract effective date. (Both are necessary, because I'm linking multiple contracts for the same customer together).

If I change the subreport linking to be the contractID, I can get it to run without failing, but it won't pull the information I need (because its on a separate contract).

If I look at the subreport contracts in question via SQL Enterprise Manager, it looks as though everything is complete, so I'm stumped.

Any ideas? Thanks in advance!
 
Rather than state "for reasons unknown to me, this report started failing without any particular reason.", state specifics, does it give an error, return incorrect data, or?

You might try opening the report and issuing a Database->Verify Database.

It may be that someone changed the database in some way.

Crystal rarely decides that it no longer wishes to run reports, it's generally an issue with the database.

Also you didn't share what failing means, so I need more info.

-k
 
Are you using Stored Procedures?

[yinyang] Madawc Williams (East Anglia, UK). Using Windows XP & Crystal 10 [yinyang]
 
Madawc - No stored procedures ...

K - Sorry about the lack of clarity. What it does is return the "Failed to return rowset" error. Then, after you click ok, you get a second error message, which is equally unhelpful - "Unknown query error."

I've tried checking through the SQL Server, but the records in both views (the subreport and the main report) are turning up complete.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top