Very hard to suspect the Outlook import process to be the source of the
problem especially given that all the other fields imported correctly (but
anything is possible). That leaves three wildcards:
#1 - An issue with the data file is in use (i.e. one possible cause could be
a header record in the CSV file that does not conform to the actual data
rows, invalid data in the mobile field, etc etc etc). Will presume that you
verified that mobile phone data actually does exist
#2 - The actual mapping of the field
#3 - How you are determining that the mobile phone number is present or not
for a given contact where it "should" exist
Some things which you can try:
#1 - open the CSV file in Excel - do mobile phone numbers show up "under"
the mobile phone column header in all records (or at least in the contacts
that you are checking n Outlook after the import is done?
#2 - import the same file but import the "office" or "home" phone number
(which otherwise worked) into the "mobile" phone field instead. If the
mobile field contains data - the issue is with your CSV file
#3 - What are you checking to determine if the Mobile field has a phone
number? If you look at the "All Field" data fields - does the mobile phone
number have data? If it does, the data is getting imported. Does the mobile
number appear in another phone (or any other) field? If it does, the data
is getting imported and the issue is one of field mapping.
Karl
___________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
http://www.contactgenie.com