On Tue, Jul 30, 2013 at 11:17 AM, Ken Dibble <[email protected]> wrote:
> This thing is driving me nuts and I'm hoping someone will see a glimmer of
> sense in it.
>
Congrats, you've got a serious gremlin error on your hands here. There
aren't a lot of techniques that can be applied within an ON SHUTDOWN
situation. If you can't reproduce the error on a testbed, and it only
infrequently happens on multiple machines, it'll be an sob to isolate. The
best you may be able to do is stick a bunch of PRINT statements in there,
in the pseudo-form:
StrToFile("C:\myapp\mylog.txt", FileToStr("C:\myapp\mylog.txt", DATETIME()
+ "Step X completed." + CHR(13)+CHR(10)))
That's pretty IO intensive, but you don't want any buffering leaving the
last few breadcrumbs in memory when the app errors out.
On application startup, you'll want to truncate or archive the old log.
In your error routine, you might want to email the log to yourself, if you
can get SMTP to work :)
--
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/cacw6n4s3dowowttoyybag3bgvxpvgkge2mjxk8gccmaa7rr...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
