2 Replies Latest reply on May 8, 2012 2:05 PM by philmodjunk

    Kill a trigger script

    RyanHenrici

      Title

      Kill a trigger script

      Post

      I'm developing a complex database solution for a client and created an OnLayoutEnter trigger script to load a different set of menus on my splash screen. Unfortunately I clicked the wrong window control and saved the file with a close window command in the script. Now when I load the file it immediately closes. Is there a way to disable or override this trigger script, I know in Access there is a keyboard command to override any "onopen" macros. My last backup is missing all the work I did today (which was a lot of tedious work and I really don't want to do it again!). Thanks so much.

       

        • 1. Re: Kill a trigger script
          Sorbsbuster

          Try opening the file while holding down 'Command' or 'Shift'.

          If you have FM Advanced you could launch the application then start the script debugging tool, and edit it from there.

          • 2. Re: Kill a trigger script
            philmodjunk

            Sometimes, if you are really lucky, you can hit esc (windows) or command period (mac) to abort the script as the file opens if you don't have advanced.

            Do you have any other scripts in this file?

            You can create a can opener file that opens your file without triggering the OnOpenScript.

            Create a new database file.

            Give it a one line script:

            Perform Script

            and specify some other script in your original file that won't harm anything if you perform it like this.

            Perform the script.

            Go to your windows menu and you'll find your original file listed in the Show Window sub menu. Select it to bring it to the front.

            You now have your file open and you can go to File Options and disable the script.

            You might also want to consider this method so that you save more copies of your script while developing it: Saving Sequential Back Ups During Development