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

Everything that AError() and AStackInfo() return along with LIST STATUS and LIST MEMORY.

And have the application send an email to you or to someone who should be responsible for dealing with it.

Also, a client recently told me about PSR.EXE, which lets you record information about all steps in a process. Gives you screenshots along the way. Unfortunately, Win 7 only.

Tamar