Without Filemaker you can re-run the import, using the legacy ID code
each time (to make the data align properly, and re-use the user import
fields. With Filemaker, you could do the same or you could create more
user import fields in ebase and use them as holders for the data. You'd
be best served, in the latter case, placing those fields on one of the
Custom screens to make it easier to do your global replaces.
Carl
Bookout wrote:
>
> When you have more custom fields than the User-1 through User-10 import
> mapping slots can fill, how can you transfer the information in your
> Legacy database into them?
>
> Henry Bookout
> North Fork Environmental Councl
> Mattituck, NY
>
> [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
> ---------------------------------------------------------------------
--
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
---------------------------------------------------------------------
