>I'm working to upgrade an affiliate database from v102 to v103. I'm looking >for a "how to" guide. Here's what I've done so far, please help me find >what I've missed and what I've done wrong. I have little confidence in the >integrity of this import. If you want to know why I'm doing this, the >affiliates v102 is buggy and unstable. The best way I know to fix the >problems is to import the data into a clean copy. > >1. Used Ebase import tool to import Record ID, Last Name, First Name from >names_.102
Be sure to re-set the auto-enter index in the field Record Number to one higher than the highest record number in your data set. Otherwise, when you start adding records, you'll have duplicate ID numbers. You need to do that with all files that have auto-enter fields, including (but not necessarily limited to - check to be sure) actions, contacts, payments. >2. Used Filemaker import tool to import remaining fields from names_.102 Presumably Updating current records using the Record number as a match field, rather than adding new records? >3. Used Ebase import tool for paymnts_1.02 See above for the auto-enter index. >4. Used Filemaker to import actions_.102, custom_.102, impenh_.102, >pledges_.102, summary_.102, contacts_.102, profile_.103 >5. There are some custom layouts on the Custom screen of v102, how do I >import those into v103? Or should I manually create them? You can copy layout elements but not layouts. In the source layout, select all and copy. Then in the destination file, create a new layout and paste (or if you are modifying a layout, select all, delete, to clear the board, then paste). >6. Used Filemaker to import srcdefs_.102 but I cannot get it to show. The >Source Code definitions in my v103 file are the same as they were before >the import. It does not show modifcations made in the v102 file. Not sure what's happening here, unless you are looking at the wrong file. srcdefs_.10x contains the source code protocol - that is, the data from which source codes are assembled. solicit_.10x contains the source codes. >How can I get the Value Lists imported? There have been significant changes >made in the v102 file which I would like to bring into v103. Value lists aren't a resource that you can import. Best you can do is copy from the value list definition in the source file and paste into the value list in the destination file. -- -- 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 ---------------------------------------------------------------------
