We have VB application (VB6 sp3) which calls the Crystal 7 (OCX calls not
API).

The app has been working fine at 70+ users sites, but recently long reports
have started to crash.

The application EXE is quite large at 5+megs.

There are about 50 forms in the app and 20+ have the crystal control on it
to print the various reports.

The problem only happens during printing and only at a handful of users, but
at these users it happens on a daily basis.  We ran tests here with 350+
pages... no problems.

At the user sites, in the middle of the long run it either GPFs or the
printer starts printing garbage.

I thought of breaking up the EXE but that is quite a bit of work.   I tried
checking the OCX and DLL files at the client to make sure they match to us
and they do.

Not sure what to do next.... any ideas?  Can Crystal handle big reports?
Is having the control on multiple forms considered duplicate OCXs as I have
heard that causes problems?

--
Dave Lund
Classic Software Corporation
28 Owen Street, Suite 203
Barrie, Ontario, Canada, L4M 3G7

www.classic.on.ca

Phone: (705) 727-0413
Fax: (705) 727-0139

Crystal needs a bit of space to work with the data it's extracted from the
DB and to prepare the pages prior to printing.  The larger the report, the
more space is needed.

I work on the assumptioon of having at least 100-200MB of spare space on the
C drive (or whereever the temp folder is pointing).  If there isn't enough
space, crystal will crash.  Make some more room, or buy them bigger disks.

It also helps to clear out those temp files as the crash will leave a lot of
them behind.

Good luck.

Sorry, customer has 4 gigs free so I don't think it's a space problem.