>Hi Kevin,
>
>If you capture to the file and look into the variables and values you will notice that variables that are deeper in call stack have method/procedure listed after the value, ie.
>
>Variable Scope Type Value Procedure Name
>SCLASS Local C "_editor" new_editor

True, but the debugger somehow knows the values of the variables in the routine currently selected on the call stack, even if the variable with the same name was defined as local or private somewhere later down the call stack. That's probably got something to do with the internal representation of the variables, that the debugger can access and we can't.