Tip: When you upgrade this way, directly importing into a fresh, new copy of ebase, select the Match Names option in the field mapping dialog box and the mapping is done for you. Record number goes to record number, etc., so you don't have to worry about manually mapping the many fields.
Carl Dave Shaw wrote: > > >We have been using ebase through filemaker for a while now but have just > >installed the new 1.03 version on a new computer and wish to transfer the > >ebase names and payments to the new computer. the "old" computer that has > >ebase on it has developed a glitch in ebase. we wanted to avoid > >transfering this glitch so we thought we would import the data via excel > >by exporting first to excel from ebase and then importing into the new > >ebase. but we are having trouble getting our legacy id to match up with > >the ebase fields. > > > >so. question 1. is there a way to do this without exporting and then > >importing. > > The shortcut is to import the records directly into the new files > from the old files. Open your new copy of ebase and for every file, > use the menu item File>Import Records to migrate the data from the > corresponding old file. Map Record Number to Record Number and the id > will remain the same. > > One major caution, and as Walt suggests, there is much information on > this in the archives, you need to reset the auto-enter index on each > file that has a field which is serial numbered - Record number in > names, invoice number in payments, and several others. Set it to one > higher than the highest number currently used, to insure you don't > get duplicate record numbers once you start entering data in the new > files. > > > > >if the answer to question 1 is NO then... > > > >question 2. what are the name datafields? name1_1 1_2 etc. (i have > >tried for two days to download the data dictionary but my computer is not > >able to access it. i get an error message. is there a problem? this has > >happened from two computers.) these keep getting messed up. so that the > >middle initial field ends up showing the first, middle, last and prefix in > >the middle initial field. ?? > > > > Names have six parts, stored in separate fields > Prefix 1 > First Name 1 > Middle Name 1 > Last Name 1 > Suffix 1 > Salutation 1 > and corresponding parts for the second name in each record. > > so, name 1-1 holds data during the import process destined for Prefix 1. > More detail on that in chapter 4 of the admin manual. > > -- > -- > Dave Shaw H4 Consulting > tel: 206-954-7526 fax: 206-625-1338 > > ------------------ > 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 > --------------------------------------------------------------------- -- Carl Paulsen New Hampshire Rivers Council 54 Portsmouth Street Concord, NH 03301 603-228-6472 603-228-0423 Fax [EMAIL PROTECTED] ------------------ 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 ---------------------------------------------------------------------
