This must have something to do with the scoring system for matching
names. It seems that if the imported vCard "FN" field does not exactly
match the BitPim "Full" name field, then other fields will likely take
higher precedence in deciding the match. This leads to some crazy
results.
I had entered phone numbers for a relative and her two next door
neighbors into the phone and then retrieved them into bitpim's database
with get phonebook. All had the same area code and similar if not the
same exchange. As with most of my relatives I edited the "Full" name
field to be a nickname because that is what I want to appear on the
phone. (eg First=John, Last=Smith, Full=Smitty; [names changed from
actual]) The neighbors were as might be expected (ie First=Fred,
Last=Johnson, Full= Fred Johnson and First=Mary, Last=Jones, Full=Mary
Jones)
Now I added addresses to John Smith, Fred Johnson, and Mary Jones in
Mac OS AddressBook and exported a vCard file. Naturally, as neighbors,
they all had similar addresses with same street, city, state and zip
code. I believe the first address, say Fred Johnson, imported
correctly because there was an exact "FN"="Full" match. I don't
remember for sure about the second (ie Mary Jones.) But BitPim
persisted in wanting to add John Smith's address as a second address in
Fred Johnson's record. This is in spite of there being an exact first
and last name match for John Smith even though full name "Smitty" did
not match "John Smith" (as it also did not match "Fred Johnson") I
presume this is due to the good match for area code, address, and zip
code taking precedence. (There was not yet an address and zip code in
Smitty's bitpim record to match on.)
I don't know what the fix to BitPim would be other than to give a
higher score to matching first and last name when there is a poor full
name match. My work-around was to temporarily edit the full name field
to be an exact match, do the import, and replace it with my preferred
familiar name.
Vic