I have a problem with one of my scripts.

The script does a few things:

-Calls a VBScript w/JobKey passed and this script then visits the job folder, and converts the cad drawings to gif images.

-Goes out to the TAGS table, searches for a job by JobKey, if there's tags it removes them (delete all found records).

-FileMaker then calls an import routine to pull in the tag records from my design software.

-Once done FileMaker searches the new tag records and omits out the records w/valid item keys and whats left it deletes (delete all found records).

This has worked fine in both locations (NY-Database local, PA-Database through VPN), but lately it seems that PA has been having issues w/the VBScript not finishing in time and causing FileMaker to crash. So what I decided to do was to put a 5second pause between steps 1 and 2, and this fixed the issue.

The problem is... if a user doesn't realize the script is still paused, and clicks one of the buttons to return to the orders screen (another table in the same database), the script will blindly continue and deletes all the order records you're currently viewing.

I almost ******* myself when I saw it deleting $250,000 worth the open orders!!!

Any suggestions are welcome.

Thanks!

Edited September 19, 200718 yr by Guest

You might have your script switch to a layout with nothing on it but a message about being patient while the import takes place. This layout should be based on the same table occurrence as the other one so that the rest of the script works the same.

You should also consider double checking that you're on the right layout before doing your Delete Found Records.

That's an idea. I could do both...

Prbly just put a few 'switch to layout:' commands in the script along the way to make sure it's going to remove the correct records.