Hi Daniel,

.NET Framework versions earlier than 2.0 swallow exceptions that occur on
background threads.

I suggest wrapping your printing code in a try..catch block.  Read the
documentation for the printing methods that you use to determine which
exceptions may be thrown and catch the ones from which your application can
recover.

To aid in debugging, you may want to add a try..catch-all exception handler
that logs any exception and then rethrows them (even those exceptions not
being handled in your code).

The framework 1.1 has an issue where it sometimes isnt ale to convert an
Access Violation into a .NET exception to throw and therefore the CLR is
terminate immediatly by windows without 1 more line of code running. I had
this for a long time with a data access rountine which would sometimes make
the application just dissappear like it was killed in task manager, I used to
have a link to the KB article about it but this was about 3 years ago now so
thats long gone.
Try handling System.Windows.Forms.Application.ThreadException event to see
if thats fired. Secondly, try running the thread inside a new app domain and
handling the unhandled exception event on the app domain from the form. It be
that the AppDomain is kill rather than the whole process.
I remember this one being a killer.

Ciaran O'Donnell