With or without the Debugger, no error occurs, when a script instruction try to access data from an unrelated table.
I think it should be reported as an error and the debugger should trap it
When we reference an unrelated field to get its name so we can target the field with ExecuteSQL without breaking queries when the name changes, should that be reported as an error?
Maybe another approach would be to always return the error you would have gotten if you had wrapped your calculation in EvaluationError ( expression )? Maybe with a toggle "Evaluation error capture on/off"?
Retrieving data ...