Henry,
Your message and situation is a bit confusing, but a few comments.
First, did you include the legacy ID with your original Names import?
There is a field in the Ebase Names and Payments files called LegacyID.
It doesn't show up on any screens. That's where the Legacy ID gets
imported for ANY import (and to which you should map your legacy ID#
each time you import new payments). Did you in fact import your legacy
ID into that field for both your names import and for the payments
import? If you didn't make sure this was done, ebase can't match the
payments, and you'd probably have to reimport the names data with the
Legacy ID attached. (You could probably do this with the update
function to avoid losing any changes you made since importing it to the
names data, but if crucial name and address data were changed, the
update may not work.)
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
---------------------------------------------------------------------
