Complex perform find script

[PKF]

I hope someone can help this neophyte. A "Samples" layout contains sample information and freezer locations on 60,000 biological samples. It is very tedious to manually create multiple sample find requests because each find requires the entry of three fields. To automate finding samples, users populate Excel records with three fields: SampleID, SampleType, and SampleDate. A script imports these fields into a related "SampleQuery" layout, but this is where the script fails. The plan was to create multiple find requests in "Samples" corresponding to the number of requested records in "SampleQuery". The script would move SampleID, SampleType, and SampleDate from each"SampleQuery" record into similar fields in the each "Samples" find request record. A Set Field command doesn't work here, perhaps because transfering information between related tables is not permissible within a script or because the script can only access information using a script parameter. Can anyone propose a solution for this confused novice?

[Genx]

Ok, first and formost... Why don't you just provide a layout with global fields for the user to enter the data to perform the find and then use these values?

As for the rest of it, I'm a bit confused at the moment, could you dumb down your structure a bit?

[LaRetta]

Hi PKF,

The plan was to create multiple find requests in "Samples" corresponding to the number of requested records in "SampleQuery". The script would move SampleID, SampleType, and SampleDate from each"SampleQuery" record into similar fields in the each "Samples" find request record.

It sounds like you need to search multiple 'like' fields here. Is this the case? Because the limitation you've hit is one of the reasons 'like' fields should be records - so searching and reporting is easier. As Genx asks, knowing your structure is critical to providing a proper response here.

LaRetta :wink2:

[comment]

I don't know - the question seems clear enough to me. The solution, unfortunately, is not that simple. The problem, in a nutshell, is that only global fields have values in Find mode. So you need to load your queries into globals in order to be able to use use them when creating find requests in the other table. See the attached example.

FindMultiRequests2.fp7.zip

[Genx]

the question seems clear enough to me

Yeh...Probably, but the right side of my brain can't put things together very well..