This problem is similar to Karl Berger's 12/12 post in this forum
regarding a
Word merge that was inserting Zipcodes into the Country field. End result
there also was your recommendation to look at import corruption, but there
is
no update on that thread from Berger.
On my end, the source of these cards is mixed. Not all imports suffer from
this, and some cards created _within_ Outlook 2003 exhibit the behaviour.
Can I send/post an example card somewhere?
--
#######22230
Russ Valentine said:
Never seen this described nor can I reproduce it. Something seems to have
corrupted these Contacts. Importing is the most common way to corrupt
Contacts. Do you think these Contacts might have been imported?
--
Russ Valentine
[MVP-Outlook]
View -> By Location shows the 76 entries with Zip Codes in the
Country/Region
column.
Double-clicking on any of these the Contact entries to open it, and
then
looking at the "General" tab -> Addresses and clicking on the detail
button
(Business... or Home...) shows values in correct fields.
Even under the "All Fields" tab -> "All Contact Fields" all values
show
in
the correct fields.
Thanks for follow-up, nice feedback system.
--
#######22230
:
Then clarify in what view and what field they do not appear correctly.
--
Russ Valentine
[MVP-Outlook]
As far as I can tell:
Regional Options -> Standards & Formats -> English (United States)
...Location -> United States
Languages -> n/a
Advanced -> non-Unicode -> English (United States)
...Code Page conv. tables -> 10000(MAC - Roman)
--
#######22230
:
Do you have your operating system's Regional and Language settings
set
correctly?
--
Russ Valentine
[MVP-Outlook]
About 76 out of ~2000 of my Contacts have the Zipcode and Country
flipped,
but not in all views. In list view they are inverted, but if I
open
the
Contact card and look at the Address in detail, the field content
appears
correctly.
Curiously, this does not propagate to my BlackBerry, or to
CardScan -
each
of these has the correct mapping, but I can no longer sort within
Outlook
reliably.
When this first appeared, I corrected all of them. Well, a few
days
later,
it's baaaack.
Any help appreciated aforehand...