>In my application when user comes across an error (bug in my code) the error message is logged into a .dbf table. But I never find the information much useful. What is missing for me to find the cause of the problem is "how" the user got to "this" place. What are the some latest keys or mouse clicks were done before the error occured.
>
>Can anybody suggest a couple of functions or methods to "trap" more useful information about an error?
>
>Thank you.
For a start, you might get the call stack, I think it would be something like this:
WriteLog("Call stack:")
for i = 1 to program(-1)
WriteLog(program(i))
next
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
