Henry,
Bookout wrote:
>
> Carl,
>
> I did not confirm, however, that ALL the records had Legacy ID's before
> importing into ebase. There were more than 2000 records and this will be
> labor intensive. However, will do.
THIS COULD BE YOUR PROBLEM. YOU SHOULD BE ABLE TO SORT ON THE LEGACY ID
FIELD IN Q&A AND EITHER AT THE BEGINNING OR END WOULD BE THE SET OF
RECORDS WITHOUT ID #s.
> 3) Since Q&A is a "flat" file, your assumption is correct that I just gave
> the 1% of names records that did not match ebase new Legacy ID numbers
> beginning with the next higher number than the highest Legacy ID number.
> This was the edited Legacy names file that I imported into ebase before
> importing corresponding payments.
IF YOU DID THIS (RE-NUMBERED THE LEGACY IDs), YOU WOULD NEED TO IMPORT
THE NAMES AGAIN WITH THE NEW LEGACY ID # AND THEN IMPORT THE PAYMENTS
(OR MODIFY THE EXISTING EBASE RECORDS SO THAT THEIR LEGACY ID # MATCHED
THE PAYMENTS). DID YOU DO THIS? IF NOT, THE PAYMENTS THAT HAVE A NEW
LEGACY ID WOULD NOT MATCH THE NAMES ALREADY IN EBASE AND THAT WOULD
CAUSE YOUR PROBLEM. STILL, I'D LOOK INTO RECORDS WITH NO LEGACY ID
NUMBERS OR PAYMENTS WITHOUT NAMES ATTACHED (THIS LATTER CASE IS LESS
LIKELY WITH A FLAT FILE, BUT IT'S WORTH LOOKING INTO).
> *Should I have also reset the Record Number index in ebase in a manner
> similar to the way you do it when you upgrade from ebase v.1.0.2 to
> v.1.0.3?*
I DON'T THINK SO, BUT THAT MAY DEPEND ON HOW YOU IMPORTED.
> 4) >Do you know how you got dupes in the 1% that did not have matching
> >payments? That is, were they dupes in your legacy data?
>
> No, I couldn't discover the reason why I got some dupes in the 1% that did
> not have matching payments in ebase. (Or, in other words, records in
> ebase that had numbers, but numbers that did not match the numbers in
> Q&A.) There were 4 dupes in the legacy data that were identified by the
> ebase import routine and these 4 were deleted as required before
> importing.
HMMMM. THIS CONFUSES ME. I'M NOT SURE I UNDERSTAND WHAT YOU ARE
CONSIDERING DUPES, ALTHOUGH I ALSO DON'T THINK THIS IS RELATED.
> I still would like to get 1996 through 2000 records straight in ebase
> before tackling 2001.
I'M SORRY THAT THIS LIST APPROACH DOESN'T ALLOW ME TO REALLY LOOK AT
YOUR LEGACY DATA AND THE RESULTING EBASE DATA, B/C IT MIGHT WELL BE
SOMETHING SIMPLE. IN THE END, YOU MAY NEED TO FIND SOMEONE TO COME IN
AND TAKE A LOOK AT YOUR DATA.
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
---------------------------------------------------------------------
