>>>My users rarely report on the problem they come across when using my application. Only way I can see that there was an error here or there is by logging the error information into a ERRORLOG.DBF. Basically all I log in this table are the following:
>>>class and method where error occurred
>>>error description (e.g. "No table is open in the current work area"
>>>and the array aStackArray
>>>
>>>But this does not seem to be sufficient for me to find what actually went wrong or if it is a bug. What else would you suggest to log on error? TIA for any suggestions.
>>Hi,
>>
>>I make use of an errorlogging procedure made by John J. Henn wich virtualy logs everything. Coding attached. The file calls a form frmErrorLogging which mimics the WIndows error message with the option to mail the log file straight away, first check / read the log or don't send.
>>
>>In case you are interested I could also mail you this form, however will need an other day as it requires translations from Dutch into English.
>>Regards,
>>Koen
>
>I got to get me a copy of that. Sounds like someone made some great improvements on my old code. Please tell me where to get it.
Hi,

I have zipped my Errorlogging inclusive a testdrive project just finished WeTransfer.
The basis of my Errorlogging project is your procedure, thanks for sharing.
Regards,
Koen