I know with java, if the bufferedstream you are using becomes full (large
amounts of data), it causes logic errors (e.g. not everything prints out).
If you flush the buffer (or have it autoflush), it behaves normally. With
Visual Basic, it may well cause the program to crash fatally (especially
with an older version).
No definite on how to solve it, but that's a hunch of mine.
-Travis
"Mark B" <remove_from
_h*********************@ihug.co.nz> wrote in message
news:bn**********@lust.ihug.co.nz...
DoCmd.OutputTo acOutputReport, globCurrentReportToBeOutput, strFileType,
strFileName, Me.CheckAutoStart
On occasion, some (not many) of our users report that when they try to
export some reports, there is a crash and our 97 runtime app shuts down.
We can't duplicate this on our development machines.
What reason(s) would cause such a crash to happen?
Thanks for any ideas.
Regards
Mark