>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.

We create a MemoryDump.txt file in case of the error that outputs display memory.