It depends on how the script is written, but since you have FileMaker Advanced, you have an easier option.
If you have a Mac system and you can hit the buttons fast enough and the script does not disable user aborts, you can press command-period to halt any currently executing script---such as the start up script. On windows systems, the Esc key does the same job.
But since you have FileMaker Advanced, do this:
Launch FileMaker without opening your file.
Select the script debugger from the tools menu.
Now use the file menu to open your file--entering a password if asked to do so.
The file will open and halt on the first script step. You can then click the red X in the debugger to halt the script--even if user aborts have been disabled.
If you want to, you can also write start up scripts to use the Get ( ModifierKeys ) function to check for specific modifier keys being down and thus can be written to exit without doing anything if such is the case.
Holding down the Shift key is meant to bypass the start-up script.
Holding down shift bypasses an auto-entered password log in and pops up the password log in instead. The start up script will still execute.
Yeah, I ended up using the Debugger this last time I needed it, doing much as you mentioned. I will give the CMD-. a shot.
But there was something else that would work. It was various control or function keys; all along the left side of the keyboard...
Unless the script was written to check for specific modifier keys and exited if they were held down, that's a new one on me.
Control-Shift is the combination. It is tricky to get the timing down correctly, though.
Launching a file from the Finder, you have to double click it first and then press the keys. Or you can right click the file, press the keys, then select 'Open' with the mouse.
Not sure if this is a FileMaker combo or OS, perhaps.
DOH! My WAY bad. Yes, there was a script checking for modifier keys when this file is opened. I just never traced it out very closely.
I did a very stupid thing, make a minute change in a script, change which I thought totally insignificant. Was very, VERY WRONG!!!!!!!! Got the hourglass of infinite death. Last backup was a day old - with many data changes in between which could not be either traced or reenterd. Your solution using debugger worked flawlessly, and saved me a huge amount of heartache. THANK YOU.
I know this is a older post before I had found this document about creating an open remote script.
This sentence is a the bottom of the above link page.
If you need to change the script, open your "opener" and try to stop the script before the file closes itself by pressing command-period in Mac OS or Esc in Windows. Or you could discard the "opener" and re-create it, incorporating your desired changes.
I have used the ESC key in windows to stop an opening script, but I didn't get it on the first try.