If you can't get past page 32,767 I would think you might have too many pages.

Since 32,768 is a power of two ( 2 to the 15th),  that is probably something in the design of the program so unlikely to have a simple registry tweak.

I agree with BigLouie,  what kind of report do you have that has 32,767+ pages ?   And what's more,  who is going to actually have the time to read that many pages?

Hi,

Does the same preview group limitation apply when the report is run and previewed through the Crystal Reports Designer?  The run time preview and Crystal Reports Designer preview are different methods of previewing reports.

If SAP is advising you to go through us (Sage) to verify and report the issue, then the issue is inherent within the SAP run time Crystal engine and is not specific to Sage 100.  

Please open a case through our support to document the case specifics.

Thanks

John Nichols

Sage

I should have clarified... The report runs fine in Crystal Reports 2011 Designer.  It also ran fine through Sage 100 version 4.40 through the Crystal Runtime.

I DID open a case... They said to document the issues here!!!!   They indicated that Tech group within Sage reviews these feeds and would assist.   Sounded odd to me!

Case number is 8003834375

Hi,  I've got the case notes.  Can you upload the report?  If not can you post the SQL statement and let me know what the primary grouping is?   If the issue is a SAP Crystal .net runtime (Sage 2013+ runtime) issue we can open a case with SAP but they may take a while to correct it.  

Not sure it will help, but try downloading and installing the latest Service Pack from SAP Crystal Reports.

scn.sap.com/.../DOC-7824

Service Pack 10 (v. 13.0.10.1385)      MSI 32 Bit   32.bit MSI

Download and run the SP on the Sage 100 workstation that contains the Crystal Designer

Thanks

John Nichols

Sage

I have attached a zip file and uploaded a very simple report I generated that exhibits the issue....  I just create a group as the Sales Order Line Key for all records in our database.  I will save data with the report in the event you don't have a sizeable system that has sufficient records to demonstrate the issue.  Remember - the report run (group tree logic) runs fine in Crystal Reports 2011 Designer... The issue will be if you add it to the Custom Reports in Sage 100 version 2013 and try to run it with the embedded runtime version.

I did test the download from SAP (the SP 10) earlier on the recommendation of SAP.  It does not seem to fix the issue - it seems like the Sage runtime version of Crystal is controlled / installed on the running of a report (instead of natively installed)????

Thank You!

Joe Huettner

HI Joe,  Thanks for the report, I just need to generate the large dataset.   The Crystal Runtime components are installed during Sage 100 install/workstation setup.   The SAP Crystal Reports SP install updates the run time components. The run time components are loaded and run during Sage 100 Printing.  

Thanks

John Nichols

Sage

Thanks.... I guess that means that the SP10 runtime update doesn't address the issue unfortunately.