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

Dmitry,

In the final analysis, no one can say for sure what caused the error.

Be defensive about the inputs. Are they within the acceptable range? Use ASSERT if the input comes from a source outside the application. Finally, try to get with the users to see exactly what caused the error.