Exporting User defined Contact Field

[Michael Greenberg]

I've played around in this area a few times now...

This is what I have found about exporting your .pst:

Microsoft does include your custom fields on export.
Microsoft does include your custom fields on import.
Microsoft doesnt iterate the newly imported pst completely so outlook wont
display the imported custom fields and their data.

Workaround:
After you import the exported pst, re-make the field names using the EXACT
field names. As soon as your done making the field, it will automatically
re-populate the data.

go ahead try it 8)

 

[Russ Valentine [MVP-Outlook]]

Or don't. Importing and exporting are never the correct way to transfer
Outlook data and you will continuer to lose a lot more than custom fields.

 

[Michael Greenberg]

if this import/export tool built into outlook isnt the correct way to
import/export data, then why, exactly is it included in the application and
secondly why include it's own application to choose to import/export to?
--
HarlesG

Or don't. Importing and exporting are never the correct way to transfer
Outlook data and you will continuer to lose a lot more than custom fields.

 

[Russ Valentine [MVP-Outlook]]

Why ask me? But do pay attention to what real users have discovered. No one
who has read the posts in this group would ever use import and export when
their data is already in Outlook format.
--
Russ Valentine
[MVP-Outlook]

if this import/export tool built into outlook isnt the correct way to
import/export data, then why, exactly is it included in the application
and
secondly why include it's own application to choose to import/export to?
--
HarlesG

Or don't. Importing and exporting are never the correct way to transfer
Outlook data and you will continuer to lose a lot more than custom
fields.
--
Russ Valentine
[MVP-Outlook]

I've played around in this area a few times now...

This is what I have found about exporting your .pst:

Microsoft does include your custom fields on export.
Microsoft does include your custom fields on import.
Microsoft doesnt iterate the newly imported pst completely so outlook
wont
display the imported custom fields and their data.

Workaround:
After you import the exported pst, re-make the field names using the
EXACT
field names. As soon as your done making the field, it will
automatically
re-populate the data.

go ahead try it 8)
--
HarlesG


:

I created a user defined field under the Customize current field -
fields -
new field in Outlook Contacts. The new field is a Yes / No type.
When I
try
to export the contacts to either MS Excel or MS Access that field is
not
available for export. Is there anyway to export ALL Contact fields --
including user created fields. I also tried to change the existing
USER
FIELD 1 field to a YES/NO type, however Outlook does not provide that
abiltiy
either. I'm using Outlook 2003 SP2

HELP Thanks

 

[Michael Greenberg]

I'm sorry I thought this was about importing & exporting, and I hadnt seen
anyone who had the information I found when playing around with outlooks
import/export for use to backup my business' data, which I run all from
outlook using mail merge thru word.

I did a search for importing/exporting user defined fields, using outlook,
and this thread came up. I did read some of the threads briefly and assumed
this post might help someone going thru some of the limitations of this
import/export feature. I accidently found when I named the custom fields in
the same folder exactly what they were in the original pst, that the
re-populated the data within the fields, automatically.

Maybe this is the wrong group of posts for this information, but I know I
didnt find anything like this, and I know it's a pretty hot topic from the
research I've done.
--
HarlesG

Why ask me? But do pay attention to what real users have discovered. No one
who has read the posts in this group would ever use import and export when
their data is already in Outlook format.
--
Russ Valentine
[MVP-Outlook]

if this import/export tool built into outlook isnt the correct way to
import/export data, then why, exactly is it included in the application
and
secondly why include it's own application to choose to import/export to?
--
HarlesG

Or don't. Importing and exporting are never the correct way to transfer
Outlook data and you will continuer to lose a lot more than custom
fields.
--
Russ Valentine
[MVP-Outlook]
message I've played around in this area a few times now...

This is what I have found about exporting your .pst:

Microsoft does include your custom fields on export.
Microsoft does include your custom fields on import.
Microsoft doesnt iterate the newly imported pst completely so outlook
wont
display the imported custom fields and their data.

Workaround:
After you import the exported pst, re-make the field names using the
EXACT
field names. As soon as your done making the field, it will
automatically
re-populate the data.

go ahead try it 8)
--
HarlesG


:

I created a user defined field under the Customize current field -
fields -
new field in Outlook Contacts. The new field is a Yes / No type.
When I
try
to export the contacts to either MS Excel or MS Access that field is
not
available for export. Is there anyway to export ALL Contact fields --
including user created fields. I also tried to change the existing
USER
FIELD 1 field to a YES/NO type, however Outlook does not provide that
abiltiy
either. I'm using Outlook 2003 SP2

HELP Thanks

 

[Thatch]

There is a product called Data Fields Manager
(http://www.datafieldsmanager.com) that lets you manage all the fields in
Outlook including copying/exchange/etc.. One of the functions is to export
all the fields and they are exported into a .csv file. Quite simple, really.

T

Thanks Karl. I've sent both links to my IT Director to check out. Have a
great weekend and thanks for your response.