Frequently - this MAPI error would occur if there is a problem within the
the CSV file itself (ergo - something isn't valid within one or more fields
which may or may not apply to every record in the CSV file). If any contacts
get imported at all - then find the last one imported and look for it in the
CSV file - the problem will most likely be related to the contact that
immediately follows it. As an aside - not every CSV file is created equally
so you may also want to open up this file in Excel and then resave it to see
if that cures the problem (if you can't import any contacts at all). Scan
the data to see if anything sticks out as being "strange" or "invalid".
Having said the above, if it's not a data issue, then it may be an internal
MAPI issue which we see happen on a regular basis with that error in
particular. You can download our ContactGenie - Message Class Modifier
product (CG-MCM is free) from our site
(
http://www.contactgenie.com/cg20dlorder.htm). This product has the latest
folder diagnostic routines we're using for our new releases. If you open up
the contact folder you're trying to import to in the "Custom Form Info"
section of the program (folder doesn't need to use a custom form) - it will
list any fields found in that folder that fail the MAPI test and you can see
if any of the fields you are trying to import to are listed. Like I said -
we see the 0x80040403 error a lot for no explainable reason and the only
solution is not to use MAPI when importing. While we have suspicions of a
pattern/cause - not something that is consistent as of yet. Just creating a
new folder (and/or a new PST file/new folder) and copying the contacts to
the new folder resolves the problem). This error can occur on both standard
and custom Outlook fields.
Karl
__________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0
"Power contact importers for MS Outlook '2000/2003"
http://www.contactgenie.com