Annetta: I haven't ever used Access, but I've imported data into new database programs (including ebase) three different times and it has seemed to me that there are two basic issues that can cause problems. One is the consistency of your original (or legacy) data entry. One data base was such a mess of inconsistent entry (primarily the efforts of one person, no less) it took me months to straighten it out before I could convert. The other issue I ran into is field value differences between your current program and the one you are moving to. For example, if you recorded a person's name as all one line, and the new program uses separate fields for first name, middle name, last name, you've got a problem. Data mapping is essential here. Read over the ebase documentation about conversion carefully and take the time to prepare your data. Make sure that the values in the fields are what you thought they should be. Be sure to map out your fields in writing (I used excel to keep it neat), that will come in handy later, believe me! Good luck. Rainie Jueschke, CFRE
begin:vcard n:Jueschke;Rainie tel;fax:(803) 799-5816 tel;work:(803) 252-9813 x-mozilla-html:FALSE org:South Carolina Fair Share version:2.1 email;internet:[EMAIL PROTECTED] title:Development Director adr;quoted-printable:;;P.O. Box 8888=0D=0A(1338 Main Street - Suite 902)=0D=0A;Columbia;SC;29202; fn:Rainie Jueschke, CFRE end:vcard
------------------ 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 ---------------------------------------------------------------------
