Sounds like an exception occurs in a thread (created by crystal reports),
and if any thread exits with an exception, then windows closes down the
whole process (program).
I.e In Short pretty well stuffed.
The only thing you could do would be to run the reporting as a separate
process, so that when it crashes, the rest of your app will not die as well.
Good luck ....
Then again I could be wrong ...
Myles.
> -----Original Message-----
> From: Steven Wild [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 31, 2000 12:11 PM
> To: Multiple recipients of list delphi
> Subject: [DUG]: Printing with Crystal
>
> We print Crystal reports from within our Delphi apps. We have recently
> traced an intermittent "bad crash" situation to printing these reports.
>
> It seems that is we are trying to print to a printer that is on a machine
> over a network, and the network connection fails then executing the report
> from within Crystal takes out the entire app with out error messages or
> any othe warning. It just goes.
>
> We need to protect from this sort of disaster. What do we do?
>
> Steven
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
