>>I've been importing legacy payments again into ebase just to make sure I
>>didn't miss any. Ebase told me that there were no
>>duplicates in itself and the import file, but when I checked the
>>duplicates had been imported.
>
>The import payment routine checks for duplicates by comparing Record
>ID, Post Date, and Amount. Only if it gets a complete match does it
>flag the payment as a dupe. Record ID in the import file is set from
>the Record ID in the names file, using a relationship based on
>Legacy ID in the names and import files. So, this all works and you
>get a dupe flag IF you imported the payments from the same source as
>the names, and IF you imported your match field from the source
>files to Legacy ID in both the names file and payments file.
>
>If you are not getting dupes flagged, I suspect you don't have a
>Legacy ID in one file or the other.
>
>>
>>Also, I can't figure out how to delete a payment that was added by
>>mistake.
>>
>>What am I overlooking?
>
>The delete button in the lower right corner of the payment entry screen.
>
>>
>>Henry Bookout
>>North Fork Environmental Council
>>Mattituck, NY
When I referrd to a payment that was added by mistake, I meant
payments that ebase imported without catching them as dupes. These do
not appear in the payment entry screen where the delete button
appears, but rather the duplicate payments are listed side by side
when you press the payments radio button for the record that contains
them; same date, same amount, same record numberin the Names_.102
file. I have not been able to discover a way to delete payments once
they appear in the payment screen of the Names_.102 file.
What confounds me is that the payments I imported for the second time
appear to meet all the conditions you describe to be recognized as
dupes: there are unigue (Legacy) ID numbers in the Question & Answer
database from which they were exported, this ID number was included
in the first field of the export file, represents the same source as
the names and the Legacy ID number of the payments and was mapped to
the Legacy ID number of ebase payment import, which you report is
stored in the names and import files.
(How can you check names and import files to check if Legacy IDs are
appropriately stored there?)
The names for which the imported payments were targeted had been
previously imported with Legacy ID numbers corresponding to the
second importation of duplicate payments. Shouldn't the second
import, then, recognize these payments as dupes?
What I am attempting to do is to verify systimatically that my newly
created ebase records are replicas of my legacy Q&A records.
Importing names a second time did a good job in this direction: most
of the names were rejected as duplicates but a few were found that
had been missed on the first name import.
It's with a second import of the payments, that my method became madness.
Is there a better way to go about verification that ebase is a
replica of your legacy file than this, short of beginning again from
the beginning and perhaps making as many mistakes?
Henry Gookout
North Fork Environmental Council
Mattituck, NY
------------------
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
---------------------------------------------------------------------
