2 Replies Latest reply on May 9, 2012 1:05 PM by apw

    beginner's error



      beginner's error


      I feel somewhat embarrassed, because I commited a stupid beginner's error, when creating hastiiy a new database after not having used Filemaker for a long time.

      The database is stuck in an eternal loop and I did of course not include 'Allow user abort' or any other precautionary measures.

      The only solution seems to me to edit the programme outside FM with an editor like BBEdit, but that doesn't work.

      Most probably the best solution would be the script debugger which is part of FM Pro Advanced, but I only have FM Pro 11.0v4.

      Does anyone have another suggestion or do I simply have to update to FM Pro Advanced ?


      Most humbly

        • 1. Re: beginner's error

          Is this script set to run when the file is opened?

          If not, just force quit Filemaker and re-open your file.

          If it is, is there another script in this file other than the one that traps you in this loop?

          If so, you can create a new file and use Perform Script in a script in this file to run some other script besides the looping script. This will open the file in the background without performing the On Open script. You can then select your file from the Windows menu, (Show window option) and get your file open without being trapped in a loop.

          PS. saving lots of copies while you work on a database file is a good habit to get into. That way, if your file gets totally messed up, you can revert to a copy that is only an hour or even a few minutes old and not have to discard as much work. It also allows you to recover from "developers remorse" when you make a major change to your file and then regret making the change.

          Saving Sequential Back Ups During Development

          • 2. Re: beginner's error

            The script was indeed set to run when the file was opened.

            By creating a new file/database I could run another script in the file and so reach the problem script without running it.

            It worked, and thanks for your advice.