I know it can be done with script triggers, but in normal scripts, can I set a to pause/resume once data has been entered into a field? I.e., A user is taken to a field, and the script waits until he has entered the data and then it takes him to another filed or layout to enter another data.

It seems that I can only pause it indefinitely or for a set number of seconds.

Thanks a million in advance.

This, imho, would be a difficult interface for a user. Why do you feel that you need this?

Thanks for your reply. Yes, maybe I am trying to do things that Filemaker is not supposed to do :Let me give you an example of where I would use a 'Pause...until user has entered data' script.

The user is viewing all data for 2007. At the top of the page I have the field 'Year'. When he clicks this field a drop down menu appears with all the years and this is the way to find and show data from a particular year i.e. 2005. This is instead of using multiple buttons for 2001, 2002, 2003 etc. Thus, this field (year) triggers a script for the user to select and view data from only the year he chooses from the drop down menu.;

Show All Records

Enter Find Mode

Go To Field (Year)

Pause/Resume script (Duration: Until user has entered data)

Set Error Capture On

Perform find

Am I doing this all wrong? Please show me the way? Thanks so much

Looks like you're on the right track. Here's a link to a demo of my standard Find script that I posted a while ago. It might also help to read the thread.

Hi Maria,

To add to Barbara's advice, the Year field in the Header of the layout that is used for selecting should be global field. If global, maybe called gYear, User selects year in browse mode (from this global drop-down called gYear) and clicks FIND button and script would look like:

Enter Find Mode [ uncheck pause ]

Set Field [ yourTable::yourYearField ; gYear ]

Perform Find [ ]

Neither is a Show All Records ever needed before you perform a Find. So User selects Year then hits button and the find is performed. This same script, attached as a trigger OnObjectModify to that global field will run just as well and eliminate the need for a button next to the drop-down.

I think between this and Barbara's demo, we should have you moving forward but if not, please speak up.

Oh and I suggest you use a Pop-Up Menu instead of a Drop-Down List.

Show All Records

Enter Find Mode

Go To Field (Year)

Pause/Resume script (Duration: Until user has entered data)

Set Error Capture On

Perform find

Actually, this method can also work. A script paused "indefinitely" will resume when user presses Enter or clicks the "Continue" button in the toolbar or clicks another button set either to 'Resume Script' or 'Perform Script + Current script: [Resume]'.