"Nickname" not available when exporting Outlook data to Access

When exporting MS Outlook data to an MS Access file you can select the
mapping of Outlook fields to corresponding Access fields using the "Map
Custom Fields" option. However, the "Nickname" field is not available for
mapping. For me, "Nickname" is far more useful than say, "Language" or
"Mileage". Why isn't "Nickname" allowed as a mappable field?

Good question.
We have no idea why.
--
Russ Valentine
[MVP-Outlook]
"Paul B." wrote in message
...
When exporting MS Outlook data to an MS Access file you can select the
mapping of Outlook fields to corresponding Access fields using the "Map
Custom Fields" option. However, the "Nickname" field is not available for
mapping. For me, "Nickname" is far more useful than say, "Language" or
"Mileage". Why isn't "Nickname" allowed as a mappable field?

Paul,
The Nickname field is populated from your autocomplete cache (NK2) file. We
have a utility that can open and of course enable you to export the nickname
data. It's called Owtlook. If you write me at www.dcs-imaging.com using
sales as the name, I will send you a document about the NK2 file that we
wrote. If you add /products.htm to our domain name it will link you to our
utility demo download/sales page.

Hope this helps,
Randy

"Paul B." wrote in message
...
When exporting MS Outlook data to an MS Access file you can select the
mapping of Outlook fields to corresponding Access fields using the "Map
Custom Fields" option. However, the "Nickname" field is not available for
mapping. For me, "Nickname" is far more useful than say, "Language" or
"Mileage". Why isn't "Nickname" allowed as a mappable field?

No it's not. It has nothing to do with the NK2 file. It is populated by the
user when he fills in the Contact Record. And for some reason it has been
left out of Outlook's export routine.
--
Russ Valentine
[MVP-Outlook]
"Randy" wrote in message
...
Paul,
The Nickname field is populated from your autocomplete cache (NK2) file.
We have a utility that can open and of course enable you to export the
nickname data. It's called Owtlook. If you write me at
www.dcs-imaging.com using sales as the name, I will send you a document
about the NK2 file that we wrote. If you add /products.htm to our domain
name it will link you to our utility demo download/sales page.

Hope this helps,
Randy

"Paul B." wrote in message
...
When exporting MS Outlook data to an MS Access file you can select the
mapping of Outlook fields to corresponding Access fields using the "Map
Custom Fields" option. However, the "Nickname" field is not available
for mapping. For me, "Nickname" is far more useful than say, "Language"
or "Mileage". Why isn't "Nickname" allowed as a mappable field?

I'm not talking about the "autocomplete" nickname when sending e-mails. I'm
talking about the "Nickname" field found under the "Details" tab of an MS
Outlook contact.. I often export my Outlook contacts to an MS Access
database, and the "nickname" field would be very useful to me in many of the
various reports that I have designed in Access.


"Randy" wrote in message
...
Paul,
The Nickname field is populated from your autocomplete cache (NK2) file.
We have a utility that can open and of course enable you to export the
nickname data. It's called Owtlook. If you write me at
www.dcs-imaging.com using sales as the name, I will send you a document
about the NK2 file that we wrote. If you add /products.htm to our domain
name it will link you to our utility demo download/sales page.

Hope this helps,
Randy

"Paul B." wrote in message
...
When exporting MS Outlook data to an MS Access file you can select the
mapping of Outlook fields to corresponding Access fields using the "Map
Custom Fields" option. However, the "Nickname" field is not available
for mapping. For me, "Nickname" is far more useful than say, "Language"
or "Mileage". Why isn't "Nickname" allowed as a mappable field?