I think the key here is your platform. RBG7 likes to have adequate resources, and for our application I recommend a minimum of 512 mb on at least w2k if not XP. W98 likely isn't up to the task. You are probably getting to the stage where W98 starts disk thrashing - the application program requires more memory, so it requests it from the OS. The OS has to swap some application memory out to disk in order to load the part of the OS required to service the request, and in the process takes memory away from the application that was just requesting additional (virtual) memory.
We had a reporting application running against a very large database in R:Base for DOS some years back on W98. When we hit this barrier you could hit ctrl-esc and it would take up to 45 minutes to get back to the desktop. Under w2k it works just fine, thank you.
I am using the latest beta (#80/W98SE) but I think this has been happening for some time although I have a feeling that earlier versions of the reports worked months, maybe as much as a year, ago - but I may not have noticed the problem then.
Does anybody have any ideas what I need to look for to correct this? Are there any limits imposed by the report on sort depth? Or row numbers? Or output file size?
Is there any significance in the failure row count being close to 32,768?
Thanks in advance for any suggestions,
Regards,
Alastair.
----------------------------------
A D B Burr,
St. Albans, UK.
----------------------------------
[EMAIL PROTECTED]
----------------------------------
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
