Client's database has several scripts which automate importing from a CSV
file for updating or adding new records. The user has to point the script to
the file to be imported. The match field for updating is the email address
field.

Before allowing the scrip to update or create new records, I need to
determine that the CSV file does not contain multiple rows of data that
contain duplicate email addresses. What's the best way to test for that
within a Filemaker script?

I suppose I could import the CSV file into a special table and then look for
duplicates within the table, then test for duplicates and abort the actual
import if any duplicate emails are found, though this would mean importing a
second time (which to me would be simpler than going through a "set field"
loop between the test table and the actual table, since the current import
script does what I want it to do). To keep this transparent to the user, I
would need to capture the filepath of the CSV file when input by the user (I
imagine to a variable which can be used to fully automate the second
import).

Does that make sense or is there a simpler way?

Thanks,

Gary



--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/