Disable Scripts?

[Moaa]

Hi,

I have a script that runs a splash screen with 'allow user abort' off.

unfortunately i think ive got a bug in the script and it runs for infinity!

Ive made a lot of changes to various scripts since i last backed it up and was wondering if there was a way of disabling scripts altogether or grab the scripts from the fp7 file?

Any help would Really be appreciated,

Thanks,

Moaa

[Fenton]

You have the Advanced version of FileMaker. So you have Script Debugger (in the Tools menu). Turn that on, BEFORE trying to open your file. Then stop the startup script before it goes into the endless loop.

If you have had to Force Quit that file, you would be much better off going to a back up which has NOT been quit forcefully; as that can damage a file. You can fairly easily copy/paste a script or scripts from one almost identical file to another.

However, try and make it so that "fairly" is very close to "identical." If you had new fields in the crashed file, recreate them in the older file (could also copy/paste, I think it's safe). But do so in the SAME creation order as the crashed file. If you had layouts, or buttons on layouts which called the new scripts, then copy/paste those to the older file.

Do all this BEFORE copy/pasting the scripts. Everything should line up. If it did not, you will see things commented out, like this, /* field name */

Never turn Allow User Abort ["Off"] until you've thoroughly tested anything with a loop. But don't feel bad. I think we've all done this (more than once :-).

[Moaa]

Thanks!

Just wondering though: I have force quit a couple of times, there is no obvious file corruption would you still reccomend copying it over?

Thanks again,

Moaa

[Fenton]

Yes, because file damage, though unlikely in this scenario,* is often not immediately apparent, and there's no sure way to tell. So, if you can go revert to a backup, you should. It is usually easier than you think, especially if a file is not complex.

*If you only Force Quit on a client machine, with a file hosted by FileMaker Server, then I wouldn't worry. But likely it was a local file, or hosted via FileMaker Pro, in which I would.

Edited September 14, 2009 by Guest