Dave Shaw wrote: > I'm not sure. If I'm reading your description right, you see a > problem with records that were created in ebase after you did the > import. But if those records were added after the import, they > shouldn't have payments in your import file.
believe it or not, our "legacy data" was spread between two MSAccess tables and an excel spreadsheet. the payment info was spread across all three files. the Access tables (in two separate databases!) were overlapping subsets of one another, with a few added columns (to contain the extra payments). the excel spreadsheet didn't have the same columns as the Access tables, but did contain name, company, and payment info (but not address -- which might have made it hard to de-dupe automatically). i chose to merge the records using eBase (to take advantage of the de-duping scripts) rather than merge them into one legacy file (yikes!) while i believe our situation to be horrific, i suspect it's not too uncommon. thus the existence of eBase, right? so the moral of the story is that if you happen to have more than one source of legacy payments, and you're noticing that some don't match up (even when you match record number to Legacy ID) make sure Legacy ID is set for the records in question. marg p.s. i did have to number my second and third payment files manually (luckily they had only about 100 records each). i did this by printing out the names and having a fried read them to me while i looked up their eBase record numbers, and she wrote them down. then i had to go back and update the Access table and the excel spreadsheet. that's why i was interested in the DupKey thing. thanks for the explanation. ------------------ 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 ---------------------------------------------------------------------
