You can use other fields that you have no use for. You can make a second
pass at the import after having moved the user fields to somewhere else.
After you get the base import done which has all the tricky stuff that ebase
reformats on the fly (phone nos, etc.) and the payments which put stuff into
multiple ebase files, you can use the bare filemaker import code matching on
the legacy id to bring in other fields. We had to do that.
> -----Original Message-----
> From: Bookout [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 29, 2001 6:59 AM
> To: TechRocks Support
> Subject: [support] Excess Custom Fields
>
>
> 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
> ---------------------------------------------------------------------
>
>
------------------
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
---------------------------------------------------------------------
