>Importing payments, immediately after setting all records to the Source
>Code Setting "Pre ebase," in the very next step in Problems, ebase reports
>that *none* of the payments have matching source codes in inbase.
>
>A lot of work has gone into preparing the Names import file into which
>these payments need to be imported.
>
>Is there any way to fix the above anomolous report that the payments do
>not have matching source codes so that these payments *can* be imported?
You very likely do not have a source code called Pre-ebase, so when
you try to assign this source code to imported payments, ebase will
warn you. If you go to the Admin screen 2 and click the button
Add/Edit Source Code records and add a source code called Pre-ebase,
you'll be able to assign this source code to the incoming payments.
--
Dave Shaw Northwest Classics, Inc
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
---------------------------------------------------------------------
