>I will step through my import attempts and summerize my problem at the end:
>Admin
>Screen 2
>Import a file into Ebase
>Import a file into names table
>Import records from a file
>Clicked on the desired import file
>mapped the fields, "Notes" were mapped into Ebase's "memo," arrows indicated
>which fields were to be imported
>Import
>Preform auto-enter options when importing: OK
>(did the import, back to import menu)
>Fixed record type
>Check for duplicates
>Dupes between import file and Ebase - find duplicates of existing names
>I chose custom, specified (only last name), replaced, specified (again only
>last name), replaced
>Clicked "Set all to update," performed tedious task of checking each record
>duplicates and setting which to update and which to create for each record
>Process all records
Thanks, this helps understand what you did.
>There is one step which I did towards the end of the process yesterday, but
>I didn't find when I walked through again just now. I received a 2 column
>list of import fields with 3 cirlces to the right of each field to indicate
>whether I want to override in an update. Some fields I checked the left most
>(to override) and the others I checked the right most circle (not override).
>I then checked the upper of 2 options at the bottom of the page. Of all
>these import fields listed, Notes or memos did not appear.
This step appears only if you have some records marked to update, and
selected Process All Records in the last step of the process. You
correctly note that memos does not appear as an option. The update
script addresses only the fields listed in the screen you mention
above. I don't know what the tradeoffs were that led the designers in
that direction, but that's the way it works.
>After doing all the above I checked random records in Home and Data entry,
>and found that Ebase had imported everything OK, only that Notes were moved
>into the memo field for only those records which were "create" files,
>whereas the "update" files did not (even though the memo field was empty for
>many of these records they remained empty).
>
The short story is that ebase is working as designed. To capture the
data from the memo field you can use the Filemaker Replace command.
Since you used the ebase import procedure, the ID number from your
old file is stored in the names_.103 file in the Legacy ID field.
Here's the procedure Jack Noll posted a couple of days ago. In place
of the Activist? field you will use the Memo field in the names file
and the Notes field in your legacy data file.
At 3:32 PM -0600 7/30/01, Jack Noll wrote:
>
>If you used the standard import routines built into ebase
>(Admin->Screen 2-> ) *and* you mapped your ID from your legacy
>database, then the old ID is stored in the names_.10x field named
>"LegacyID". You can create a relationship from names_.10x to the
>legacy database based upon the "LegacyID" field in names_.10x
>matching the ID field from your legacy file; name the relationship
>"Legacy".
>
>Now that you have this relationship, get to the "Activist" screen.
>Hit the "Find All" button. Now, place your cursor into the
>"Activist?" field and select Scripts->FMPro Replace Command.
>Replace with the Volunteer Y/N field from the relationship named
>"Legacy". Next, do likewise with the memo field.
>
>This is really kind of cool because you're driving the replacement
>from the names_.10x file, but you're actually replacing data in the
>profile_.10x file with information in the legacy 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
---------------------------------------------------------------------
