Dave Shaw wrote:

> Yes, the import process works for the run-time. The mentions in the
> manual seem to be mostly background on the way FileMaker (and
> therefore the runtime) works. If you have data that doesn't fit
> neatly into one of the import fields listed in the manual, you'll be
> able to import it into one of the User Fields, but you won't be able
> to see it without creating a new field and putting it on a layout,
> which will require FileMaker.
> 

You CAN, however, move that data from the User Fields to an unused but
visible ebase field by doing a "calculated replace".  It's a little
tricky for a beginner, but really a simple process.  If you need to do
that but don't know how, inquire through the list.

Carl

-- 
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
---------------------------------------------------------------------

Reply via email to