I have my standard Error Log routine in almost all procedures.
Depending on how the log call is set in a procedure it will generate:
1) Msg Only
2) Log Only
3) Msg and Log
What I've found in realtime, is that at times when an error occurs a particular procedure may be called multiple times. With "Msg Only", or "Msg and Log" this may generate multiple message boxes Until I run out of memory or App times out.
Using "Log Only" solves the above problems, but then one has to remember to check the log at the end each day or set a flag to trigger a reminder that the log has new data. It does not give immediate feedback an error has occurred.
Having a log error routine at the procedure level helps, but I've seen some programs which generate logs of almost everything that occurs within a procedure. I can't image each procedure has a "call log" after almost every line code, but maybe it does? However, going with this concept of generating a log for almost everything executed would generate a huge log in realtime.
Anyone have a suggestion to:
1) Trying to get as much error log data a possible in realtime
but keep the volume down?
2) Keep the App from running out of memory because of Msgbox calls when multiple calls are being made to a procedure that errors?
Depending on how the log call is set in a procedure it will generate:
1) Msg Only
2) Log Only
3) Msg and Log
What I've found in realtime, is that at times when an error occurs a particular procedure may be called multiple times. With "Msg Only", or "Msg and Log" this may generate multiple message boxes Until I run out of memory or App times out.
Using "Log Only" solves the above problems, but then one has to remember to check the log at the end each day or set a flag to trigger a reminder that the log has new data. It does not give immediate feedback an error has occurred.
Having a log error routine at the procedure level helps, but I've seen some programs which generate logs of almost everything that occurs within a procedure. I can't image each procedure has a "call log" after almost every line code, but maybe it does? However, going with this concept of generating a log for almost everything executed would generate a huge log in realtime.
Anyone have a suggestion to:
1) Trying to get as much error log data a possible in realtime
but keep the volume down?
2) Keep the App from running out of memory because of Msgbox calls when multiple calls are being made to a procedure that errors?