Kevin,

I am using DISPLAY MEMORY catpured to a file.
HTH.


>The problem is that if procedure 'A' throws an error which
>triggers the ON ERROR routine, there is no way to
>know what the value of the variables in the offending procedure
>are.
>
>Any thoughts on this?
>
>
>
>>No.
>>
>>>Is there any way to navigate back up through the call stack to retrieve variable values for error logging?
>>>
>>>The LIST MEMORY command only shows public variables and variables local to the error handler routine,
>>>so I cannot see the contents of variables in the function that triggered the ON ERROR.