>Anybody know the trick to importing a secondary name to the correct >spot? If I try to import just the first name of a spouse to a >record, it is put in the last name field regardless of where I map >it.
The import routine does some pretty complex parsing to figure out where to put the pieces of compound names like John & Susan Smith all in the same field. You might have found an edge of its capabilities. I'd say you need a last name to go with the first name if the two first names are in separate fields. Is your source data in some form where you could search for records with a first name but no last name on the secondary listing and fill in the last name from the last name of the primary listing? >And by the way, is the version 1 searchable support stuff back online? Bob announced today that there were some revisions to the web site, but I don't see the version 1 support material back up yet. -- -- 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 ---------------------------------------------------------------------
