Phil- Wednesday, June 17, 2009, 2:20:03 PM, you wrote:
> So my question is: > When 'errorDialog' is executed, is its <executionError> parameter (which > contains error description info) the only data that's available to help > us get at the cause of the error? I can live with that, but I would just > like to know. Or am I missing something? Can you handle the traceError message instead (put this into a frontscript)? on traceError pHandlerName, pLineNumber, pCharOffset, pErrorInfo, pObjectID, pErrorType answer "got traceError" put "executionContexts=" & the executionContexts & cr after msg set the debugContext to line 1 of the executionContexts --put "debugContext=" & the debugContext & cr after msg debugdo "put the variableNames & cr after msg" debugdo "put myVar & cr after msg" set the debugContext to empty pass traceError end traceError -- -Mark Wieder mwie...@ahsoftware.net _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
