Error detected by database dll or not enough memory to complete operat

[trialbyfire]

I am getting an error on an inventory report that I designed using crystal 8.5. The report used to work and now everytime we run the report it is taking approx. 3 1/2 hrs to run and gives me an error stating either
"error detected by database dll"
or
"Not enough memory to complete operation."

The report is published and compiled using crystals compiling program and runs fine, about 1 1/2 minutes if running to window. However once we go to export it to excel the above happens and it takes forever.

I am using and ODBC connection to a Progress Database. The selection Criteria in the report are as follows.
{inventory.level} = 2 and
{category.category-code} in
["MLSPA", "MLS", "BUD BRND", "MILLER", "COMBO", "AFL", "AFL2", "AIRFORCE", "ARMY", "MLB", "MLBPA", "NBA", "NBAP", "NHL", "NHLPA", "NLBA", "PROFISH", "WNBA", "WWF"] and
{inventory.level-key-2} = "00000001" and
{category.system-id} = "DPM"

The report returns about 13000 records. Is there anyway to speed this up and cut the error?

 

[RJFost]

Exporting- especially to Excel- is an incredible RAM hog. I've always pushed the report to a .csv file, then imported THAT into Excel (granted, this is problematic with header & footer sections).

What's worse, if you've got a subreport in a repeated section (detail line, page header/footer, etc.), CR has to instantiate a new object for each occurrence of the subreport, then hold them ALL in memory until the entire report is generated. Fire up the export, then launch Task Manager & watch the RAM usage inexorably creep higher & higher. Sounds like you're just running out of RAM before the report runs out of records.

(Hey, if you play your cards right, see if the boss will take a Gordian Knot approach & just buy you a new screamer P4 workstation with gobs of RAM & a big honkin' HDD)

 

[trialbyfire]

RJFrost,

Thanks for the input. Unfortunately I was aware of the memory issues. Was just hoping that there was a way to work around this. I am running the report on a compaq P4 1.4 GHZ machine with almost a gig of ram. The other users are having the majority of the problem. I think like, you said, that the biggest issue lies in the fact that I have a two subreports that are running in the detail level of the report. One of them is referencing and entirely different set of databases. I was hoping there was another fix to this but alas it does not sound like it. Thank-you for your time. It looks as if I will have to split the report into three smaller and more manageable sections. I too tried the .csv, text etc... but all of those played havock to much with the report headings and it duplicated the first subreport records throughout the entire report.

Thanks though,

 

[RJFost]

Take a look at conditionally suppressing the subreport, based on a value (or whatever) in the main report. If you don't generate the sub, there's no object instantiated; but if you're running the subs no matter what, this will always be a problem. Additionally, you might check the result of moving the subs to detail section clones (Insert Section Below); then you can suppress Detail_B, Detail_C, what have you, before the subreports are even an issue.

 

[trialbyfire]

unfortunately I need the subreports to be initiated. The columns in the spreadsheet are as follows

Category, Sub-category, Product Code, On hand Quantity, On order quantity, pending sales order quantity, backorder quantity, total available quantity, Expected arrival date (from oversees factory), Factory PO number, Supplier.

The last three columns are subreports. We need these to come in the detail line of the report. I am going to try the report on one our servers. See if that helps.

Thanks again,