By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,107 Members | 1,318 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,107 IT Pros & Developers. It's quick & easy.

Why would DoCmd.OutputTo occasionally crash?

P: n/a
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

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
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

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.