The fact that the database is already in Filemaker makes this a fairly simple process, provided that you're fairly competent with Filemaker. If you're not (and I'm really quite serious here) you should be paying someone who *is* to do this work. You'll save tons of time and frustration. That said, the first step is to create a new number field in the legacy db, then globally replace that field with serial numbers starting with 1 and incrementing by 1. You now have unique id's for the legacy db. Make sure to map this field to the LegacyID field in the import process. Next, when you want to import the payments, you may want to do them in chunks. You probably have a series of fields named something like "Amt99", "Date99", "Amt00", "Date00", etc. Find all of the records in the legacy file where "Amt99" is greater than 0. Then, import payments using the legacy file as the source. Map the LegacyID, Amt99, Date99 and any other fields pertinent to the payments made in 1999 to the appropriate fields in the payment import file. Once this set of payments is in the payment import file, you can do global replacements (if needed) for Payment For, Start Date and other fields. Repeat this process for each set of payments until you've imported all of the payment data. Once I've imported names and payments, I then establish a relationship between the names_.10x file and the legacy db. This allows me to easily perform global replacements of info in the names_.10x or profile_.10x file with info in the legacy file anytime I want after the conversion. So, to get your affiliations data into ebase, you get to the Bio screen, Find All, place your cursor into the Affiliations field and do a global replacement from Legacy::Affiliations. >I am about to convert an existing filemaker pro db into ebase. The legacy >db has not only contact information but also affiliation and payment >information. I am totally comfortable using the ebase import wizard to >pull in the contact information but I don't see a way to import my >multi-value affiliation field into ebase's affiliation field. The >BIO:Affiliation field does not show up in the import field listing. Any >suggestions? > >Question #2 - I would like to bring over my payment history as payments in >ebase... what is the best way to proceed after importing the Names data? >The legacy db does not store unique id #'s on the records so I'm not sure >I can use the ebase import wizard to bring it over (i.e., How would it >match the payments to the correct names record?) --------------------------------------------------------------------- Jack Noll - ebase consultant and wildlife advocate Check out a *great* program at www.beardogs.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 ---------------------------------------------------------------------
