It sounds like you are using the FileMaker import menu rather than the import process automated by the Admin script. This is not a good idea because the ebase process correctly creates the related records which the FileMaker process knows nothing about. You should be using your Student ID as the Legacy ID. The Legacy ID is not visible on any of the supplied layouts but for your group it sounds like it is an important field that you should have on your screens.
> -----Original Message----- > From: Colin Cooler [mailto:[EMAIL PROTECTED]] > Sent: Sunday, October 28, 2001 3:59 PM > To: TechRocks Support > Subject: [support] Importing Legacy Data > > > Hi All, > > First let me say that I read the appropriate sections in the > Administrator's > manual first but didn't find my answer. > > I work for a non-profit group called Right Moves for Youth. Last year, I > used the Student IDs of our kids (obtained from an extract of our local > schools system's database) and mapped this field to the "USER ID" field in > ebase. Once ebase record numbers have been created after the > import process > and these kids are in our database, I of course rely on the ebase "Record > Number" for all subsequent activities. > > However, at the beginning of this year, the only way for me to > tell whether > or not I already have a kid in our database is to use the USER ID (Student > ID) as a means of comparison with the new extracted tab-delimited > file that > I get from our school system. So during the ebase import routines, I map > the Student ID field in my school system file to the USER ID > field in ebase > (and map the remaining fields accordingly). I select this duo as > the "match > field" combination, select "Update matching records in the current found > set" and check "Add remaining records." > > I assumed that following these procedures would mean that ebase would > identify which USER IDs (Student ID#s) already existed in ebase (simply > update the remaining fields for these records) and then only create NEW > records for the students which were not already in ebase. But it doesn't > work! Instead, ebase shows that there are NO records to "update" and that > there are only NEW records to create. Consequently, I get many duplicate > student records when I finish the import process. > > What am I missing? (I've checked to make sure that both "Student ID" and > "USER ID" are the same data type) > > Thanks for any help! > > (FM Server on NT4 Server; > FMPro 5 on W98 clients) > > > ------------------ > Reminder to each recipient: To change your list account preferences, go to > http://email.sparklist.com/scripts/lyris.pl?enter=support and > enter the email address you used to subscribe to the ebase > support list:: [EMAIL PROTECTED] > > To unsubscribe send a blank email to [EMAIL PROTECTED] > --------------------------------------------------------------------- > ebase - Relationship Management for Nonprofits, http://www.ebase.org > --------------------------------------------------------------------- > > ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
