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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No rowset was returned for this table, query or procedure.

Status
Not open for further replies.

PerrinA

Programmer
Jul 26, 2001
15
US
When I try to Previewcertain files i get this error:
No rowset was returned for this table, query or procedure.
When I hit okay I get this error:
Error detected by database DLL.
I'm guessing that this problem has come up before and if it has can someone direct me to the solution. Thank you.
Aybara.
 
Which version of CR are you using? What is your database?
 
I am using version 8.5. The database is in Excell.
 
I am also encountering this error. I am using CR 8.5 professional and accessing a Jet database via ADO. When I run the same report in CR 9 professional, the error is somewhat more informative:
Failed to open a rowset
Details: ADO Error Code 0x80040e14
Source: Microsoft Jet Database Engine
Description: Join type not supported
SQL State: 3000
Native Error: -540806602
 
I have figured out the problem (my problem) at least. It seems that when you convert from DAO to ADO in Crystal 8.5 something does not get cleaned up in the conversion. I reran the report in Crystal Pro 9 and reset up the database location using ADO drivers. Everything works fine. BUT if you decided to change the linking on a table you must change all tables in that "chain". (ex If you have three tables in a row, the linking between all tables must be changed.) I don't feel that is right for alot of the data I am trying to retrieve, but as of now Crystal seems to be pulling the correct information. If you change the linking on all links, the error will go away.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top