I have a layout (CLIENT DATA) that has a fixed field (CLIENT STATUS).

On a different layout (NEW SEARCH) there is a calculated field (DQ DATE RANGE) that is a based on an entry of a starting date (e.g. entry of  June 7th generates a text field of 3/30…6/7).

A third layout (LINE BY LINE DATA) contains a large number of records that are related to the first layout by an ID number. This layout has fields that show data for a  transaction date, a Client Status field, and other fields related to the transaction,

I am trying to construct a script that performs a find in the LINE BY LINE layout. This requires placing the layout in find mode, placing the date range (from NEW SEARCH layout) in the date field, and placing the Client Status (from the CLIENT DATA layout) in the Status field.

I have tried everything I can think of, but I cannot get it to work.

I seemed to be simple to use the following:

Enter Find mode
Set Field (LINE BY LINE::CLIENT STATUS::CLIENT DATA;;CLIENT STATUS
Set Field (LINE BY LINE::PICKUP DATE; NEW SEARCH::DQ DATE RANGE

Perform Find

I tried a few other things (copy & paste. etc.) but nothing seems to work. What am I missing here?

The attached file uses a sign on name of JC, with no password.

TIA

TEST_FILE.fmp12

Its kind of hard to tell what you want to search. IOW explain the workflow.

1.  Your relationships to the New Search layout is wrong, actually I believe it's unnecessary, but can not tell from the sample file.

2.  Your date range field needs to be Global storage.  Once I made it global it worked (a little).

The basic construct would be (to make it a little easier).

Grab the date range in a variable (not really necessary as its global but good practice.

Grab anything else you want to search into variables, like status, and pickup day.

Enter find mode

Switch layouts

Set field steps, 1 for each variable, to the variable

Perform Find.

Like I said, if you can explain the workflow better, more help would be easier.

Don't need new record request, but don't know for sure.

Edited June 27, 20187 yr by Steve Martino

Without stringing this out, your suggestion of using a global field solved my problem...Thanks!