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!

Access Error

Status
Not open for further replies.

lgmin

Programmer
May 20, 2005
71
US
I am using Crystal Reports 10.0 and have SP2 installed. I have a report that has 19 subreports in their own footers. When I view the report in Crystal, it works fine, but when I publish it to the web with the crystal console manager, I get a error message "cannot open a rowset". My DSN looks fine and I have other reports going to this same database without a problem. There are no parameters on this report. Any suggestions or ideas on why this is not opening? Thanks.

lg
 
I've heard of "Failed to open a rowset" within CE, but not cannot open a rowset, perhaps it's a proprietary error returned by your database.

What database/connectivity are you using?

Does the CE server have the exact same connectivty and permissions?

-k
 
My mistake. The message is "Failed to Open a rowset". I have an ODBC connection set up to an Access database. The permissions are the same on the server. I have other reports going to this database, so this report has me stumped. The only difference between the reports is that the one that I am having difficulty with has unlinked subreports, where the other one has linked subreports.

Any ideas?

Thanks.
 
I think I found the problem, but don't like the solution, so if anyone has any ideas I'd love to hear them.

My database had many linked tables, and Crystal doesn't seem to be able to handle them, is that correct? I copied the tables into the database and got rid of the links, and it is working fine now.

Does anyone know how to work around this so I don't have to keep duplicate tables and remember to update both of them?

Thanks.

lg
 
Crystal handles joins just fine.

Prehaps you should try switching the connectivity from native to ODBC or vice versa depending upon what you have.

A better way to approach this would be to create a Query within Access as the datasource for your Crystal report. Remember to turn on the File->Options->Database->Show Views to see the query as a datasource.

-k

-k
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top