See that is the exact problem. Because when enabled, the remoteScriptDebugger says there is an error, but cannot show me where the error is because the script is locked, I have no clue as to what script (if any) is causing the issue. That is why I asked if anyone had the password to the remoteScriptDebugger, so I could trace it back.
And to further complicate things, once I remove the remoteScriptDebugger, none of my regular scripts are failing, unless it is failing silently which lands me right where I started. Anyway, at least I have a workaround. Bob S On Dec 11, 2023, at 11:19 AM, J. Landman Gay via use-livecode <use-livecode@lists.runrev.com> wrote: If you have a reproducible script it would be something LC probably should know about in a bug report. -- Jacqueline Landman Gay | jac...@hyperactivesw.com<mailto:jac...@hyperactivesw.com> HyperActive Software | http://www.hyperactivesw.com<http://www.hyperactivesw.com/> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
