I have a script that loops through my project table and performs various finds based on a presence of a validation code. Example: my ExceptionCodes field can contain many code values (e.g. "P1 P2 P3" ,etc) in the same field. Each code represents a different validation error.

After each find is performed, is there a way to copy the found set into another table? Each found set would then need to append the found records to the new table.

After the script is complete the new table will contain all records that had validation errors, with some records showing multiple times if they had mutiple errors.

The thought behind this is then i could easily group the records by project and report on them, showing all of the validation errors for a project.

Is this possible? Thanks for any guidance.

Does this mean that you have two set's of of the same data, what happens if one of them gets altered, how would you syncronize?

My take on this is that it's an unhelathy approach likely to produce unreliable data. You should let your records stay in the original table.

http://www.filemakermagazine.com/secured/544/SavedSearches_full.mov

...gives you a fine method, but you need to subscripe the service provided ... but as such does it exploit that you can get into each field in the list of requests by:

http://www.filemaker.com/help/Script-Steps74.html

...where each value encountered is saved in global field because it holds value regardless of mode being find or browse. Today would $$ or $ variabels be just as convenient measures perhaps even with the use of:

http://www.briandunning.com/cf/71

...the gathered info is then put into records which can be recalled in a jiff.

--sd

i figured a way to do in by just importing into another table within the script.

it does create duplicate data, but only until the report is run, then the data is erased from the second table. it is just used for reporting purposes for a one-time conversion file.

if this were a living application i would use a more thought-out approach.

Wouldn't it be more obvious to deal with the found set where it resides, it's pretty obivous that the report not really pulls relational data ... is the data properly normalized. Do you have a series of imports to cope with it, or do you import from unstored calc'fields forgetting the change of tunneling wich arrived by fm7?

--sd