>>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
I am taking notes of all suggestions. And will check out this PSR.EXE. However, I can't make my application automatically email; many clients "warn" that they do not like this. Probably mainly concerned about losing confidential information. I periodically connect and check myself.
Thank you very much.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
