Import/Export Logs

[cliffordpg]

Not very experienced with this, but is there way to get logs fo
importing/exporting contacts for outlook 2007?
For example, showing how many contacts were actually imported
duplicates detected, how many failed and details (name/email address
of the contacts that failed to be importe

 

[Russ Valentine]

Since importing and exporting is not a recommended way to transfer Outlook
Contact data in most scenarios, one must wonder why you are using it and why
you think you want to track it. Your post is very deficient in details.

 

[cliffordpg]

Well we have a lot of legacy data in excel format from about 7years ag
and since they are not all of the same format, I developed a header an
create these contacts in CSV for import into Outlook. We use Outloo
2007 with Exchange 2003.

 

[Russ Valentine]

Unfortunately, I am aware of no log that Outlook maintains. Did you actually
import into an Outlook installation or into Exchange?
--
Russ Valentine

Well we have a lot of legacy data in excel format from about 7years ago
and since they are not all of the same format, I developed a header and
create these contacts in CSV for import into Outlook. We use Outlook
2007 with Exchange 2003.

[/QUOTE]

 

[Karl Timmermans]

#1 - There is no log of any kind when importing using Outlook import/export
wizard
#2 - Not exactly sure what you mean by "developed a header" unless you just
mean that you added a header row containing field names. More importantly,
fields should be manually mapped when importing. You should not rely on any
kind of "auto-mapping" to ensure there are no issues regardless of how you
named your fields (just takes a couple of extra seconds to avoid all kinds
of potential aggravation)
#3 - if you concern is "data validity" for you legacy data - a simple
solution to determine the quality of all your data would be to create an MS
Access database with a table defined using the expected field types (i.e. a
date field should be defined as such etc). Import either your CSV or Excel
data into ther MS Access table and you will immediately find any
discrepancies. If there are none, you can import either your CSV or Access
data into Outlook with full confidence that everything will be imported
(but to emphasize - based on manually mapping the fields)

Aside from that - the only other limitation with the Outlook import/export
wizard is that it can only import to 'standard" fields. If you need
anything imported into any user-defined fields - you will need to either
write your own code or use a 3rd party utility - (ContactGenie QuickPort or
DataPort are two such options http://www.contactgenie.com - both of which
create a StatsLog and DataErrorLog (if required))

Karl
--
____________________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - QuickPort/DataPort/Exporter/Toolkit/Duplicate Contact Mgr
"Contact import/export/data management tools for Outlook '2000/2010"
http://www.contactgenie.com

Well we have a lot of legacy data in excel format from about 7years ago
and since they are not all of the same format, I developed a header and
create these contacts in CSV for import into Outlook. We use Outlook
2007 with Exchange 2003.

[/QUOTE]

 

[cliffordpg]

The outlook installation is on a standalone pc while our email serve
has exchange 2k3. Its too bad that logs cannot or some form of tracin
cannot be set for a particular outlook operation.