1 of 1 people found this helpful
Open script debugger then open the file.
You will be able to terminate the errant script as soon as it starts running.
You will need advanced to use debugger.
If you don't have advanced, you can probably use the esc key in windows or command period on a Mac to halt the script.
You can also set up a new file that uses perform some other "safe" script in your first file as a way to open it without tripping the trigger that is performing the script each time that you open the file.
Thanks for prompt reply. Unfortunately, the menu for opening script debugger – and everything else – is inactive. Only the custom dialog box is active. Kill it and it immediately comes back. I’ve even tried to experiment with the timing – hoping to get in an Esc between refreshes of that dialog box – but so far no luck.
Responded too quickly. Hadn’t realized that I could open FM the application, instead of a specific file, then open the Script debugger in a separate window, then open the database file. That works and what a life saver.
Thanks so much.
Thanks very much for this idea. In the future, I’ll have users that do not have Advanced so this may be the solution if the problem recurs in that environment.
You should also consider making frequent back up copies during development.