The issue is that your Access data is numeric, while the values in Outlook are strings. This article describes the problem and suggests a couple of solutions: http://support.microsoft.com/kb/238323/

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
Hello Sue:
Tried both the solutions in the article and nothing solved my problem. I
don't have data that contains hyphens, or parentheses as the article claimed,
and even when I changed the data to a text form (my program doesn't
specifically allow me to save it as a csv. file, but lumps them all under
text) Outlook wouldn't allow me to import that form. I saw where it stated
the zip codes are coming up with a decimal point followed by 3 zeros, but
then it didn't give a solution for that particular problem.
I tried going into the design view on the individual Access table and
changing the decimal entry from auto to zero, but that didn't help.
I also would like to know how I can change the existing data to add wording
to the effect of Apt. # 1701 to designate it as such in the Outlook address.
Can that be changed in the Assess design view or not? My problem the previous
individual who designed the initial Assess database I am now working from.
> The issue is that your Access data is numeric, while the values in Outlook are strings. This article describes the problem and suggests a couple of solutions: http://support.microsoft.com/kb/238323/
>
[quoted text clipped - 14 lines]
> >> >> > features of the Outlook program. I am not as schooled in the working of
> >> >> > Access and feel the Outlook functions would better serve our current needs.
Sue Mosher [MVP-Outlook] - 21 Nov 2006 14:02 GMT
Ideally, the zip code field should be not a number but a text, so it can support Zip+4. Same with apartment number. Sounds like the database designer never heard of Apartment 3G.
If it were my project, I might use a make table query to create a new table that has the existing fields that have no problem + a text (not numeric) field for the zip + a text field for the apartment number. See http://www.ehow.com/how_14046_create-make-table.html

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> Hello Sue:
> Tried both the solutions in the article and nothing solved my problem. I
[quoted text clipped - 12 lines]
>
>> The issue is that your Access data is numeric, while the values in Outlook are strings. This article describes the problem and suggests a couple of solutions: http://support.microsoft.com/kb/238323/
>>
>> > when I went into Outlook and opened the import
[quoted text clipped - 13 lines]
>> >> >> > features of the Outlook program. I am not as schooled in the working of
>> >> >> > Access and feel the Outlook functions would better serve our current needs.