Failed to save document

[scc]

Here's my quetion(s).

Is there a limit to the size a Crystal file can be, assuming there's plenty of room on the hard drive?

Is there a limit to the number of records?

First of all some facts:

This report was designed using Crystal 8.5. This report is being ran remotely (off-site and populated with data from our server). There are no subreports in the report. This report is being ran directly from Crystal Reports (8.5) to populate it with data so that it can be checked before going into production. The report brings back about 750,000 records.

Here's the problem:
When I go to save the report (with data), doing a Save As to give it a new name, I get the following error messaage: "Failed to save document." When I clicked the "Ok" button, a second message stating "Not supported" was displayed.

Any ideas? Is this because it is remote? I tried running the same report where it wasn't remote, but with less data (since it was hitting during production hours), and didn't have this problem.

Thanks for any insight into this you can give.

 

[IdoMillet]

I'm not aware of a file size limitation, but you could test the issue by applying a record selection that limits the number of records.

Just curious, why do you need to save 750k records worth of data in a Crystal report?

Cheers,
- Ido

CUT, Visual CUT, and DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.

http://www.MilletSoftware.com

 

[scc]

Ido -

Again, just QAing before going into production. The automated Crystal Report has to match the MSAccess report that is currently being produced via many iterations of manual processing through MSAccess. The report is a YTD report for Data Analysis and that's how many records (line items) there are in the report.

It is a monthly YTD report. In this instance, the final report will get exported as a .pdf file and fortunately that does work. The file is saved to a folder on the network for users to be able to reference not only now but for future to see a snapshot in time of business.

However, there could be (?) times that we need to save an .rpt file of this size, as that's the type of file our Report Manager application uses. Therefore, it would be good to know of any CR limitations.

Will try a smaller file remotely just to see if we get the same error.

Thanks for responding.

 

[IdoMillet]

Consider exporting to ODBC, instead of saving in rpt. Your objective is to compare detailed data and you don't want to do that manually by looking at 2 reports (each with 750,000 records!).

By exporting to an Access table via ODBC (from Crystal) you can then create queries in Access that compare the 2 data sets.

Alternatively, if all you need to do is compare symmary information, then use a summary data set (either via a summary query or via perform Grouping on server) so that Crystal gets much fewer records.

Cheers,
- Ido

CUT, Visual CUT, and DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.

http://www.MilletSoftware.com