how does the import/export function potentially corrupt files?...

  • Thread starter Thread starter Rob
  • Start date Start date
R

Rob

i have yet to transfer my contacts from my old computer. i have an odd issue
with my new system that needs to be resolved beforehand. but the Outlook
techs from Dell and Microsoft that I have spoken to (probably 5 or 6)
recommend that I use the import/export feature, although they recognize that
copying the default .pst file is another alternative.

just curious why this is. thanks for any input.
 
it should not corrupt files but import/export will mess up the modified
dates and may mess up the profile.

what format is the pst? what version of outlook is on the new system? The
best method depends on the answer to these questions.











** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **
 
i have Outlook 2003 with XP on my old computer and OL 2007 on my new computer
which runs Vista.
 
i did casually puruse this group but most replys to individuals that asked
about import/export were "this question is answered countless times every
day" followed by several links.

my interest is more about "how" does it corrupt.


Russ Valentine said:
With a casual perusal of this group you would quickly learn why you never
use import and export to transfer Outlook data, unless you have some need to
lose or corrupt it. If you can't find a relevant post, tell us why and we
can repost it for you.

In your case you would repair your current data file, copy it, and open it
in the other installation.
--
Russ Valentine
[MVP-Outlook]
Rob said:
i have yet to transfer my contacts from my old computer. i have an odd
issue
with my new system that needs to be resolved beforehand. but the Outlook
techs from Dell and Microsoft that I have spoken to (probably 5 or 6)
recommend that I use the import/export feature, although they recognize
that
copying the default .pst file is another alternative.

just curious why this is. thanks for any input.
Click to expand...
Click to expand...
 
Rob said:
i did casually puruse this group but most replys to individuals that asked
about import/export were "this question is answered countless times every
day" followed by several links.

my interest is more about "how" does it corrupt.
Click to expand...

Probably in the same way that a pst file on a network can corrupt. The
"Export" function is used from within Outlook, ie the pst file is in use. If
during the export action Outlook does a send/receive for example, no two
functions can access the pst file at the same time, and so we get the
potential for corruption. (I think....someone more technical may give a
better explanation)
 
With a casual perusal of this group you would quickly learn why you never
use import and export to transfer Outlook data, unless you have some need to
lose or corrupt it. If you can't find a relevant post, tell us why and we
can repost it for you.

In your case you would repair your current data file, copy it, and open it
in the other installation.
 
Did any of the tech's at either MS or Dell that you spoke with happen to
mention "WHY" they recommended "import/export" over opening the PST file in
the new installation? It absolutely boggles my mind why anyone would
recommend "import/export" as the preferred venue (am specifically referring
to PST2PST) other than it being a "textbook" response. Have yet to find
anything on or have anyone provide an explanation as to why PST2PST
import/export would be a better or preferred approach. Given the nature and
focus of our products - this is a topic that is more than just a passing
interest and, in fact, we highly recommend "against" ANY kind of
import/export, including using our own products, if the <sole> purpose is to
move from one installation to another - just absolutely not necessary.

Aside from all else, we've had to deal with "imported/exported" data from
customers on more than one occasion and have run across all kinds of
"anomalies" with the underlying data (or as might otherwise be referred to
in polite company as "undocumented features" making a given issue look like
it's the "other" program's problem).

More to point to your exact question "how does the import/export function
potentially corrupt files?" - it's hard enough to get all the info as to
what or how Outlook is "supposed" to do things when everything works
"correctly" let alone try and document all the ways that things can get
screwed up across multiple versions of Outlook particularly when the
internal processes that Outlook uses don't always seem to be the same as
those provided to the development community.

Karl
___________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
http://www.contactgenie.com


Rob said:
i did casually puruse this group but most replys to individuals that asked
about import/export were "this question is answered countless times every
day" followed by several links.

my interest is more about "how" does it corrupt.


Russ Valentine said:
With a casual perusal of this group you would quickly learn why you never
use import and export to transfer Outlook data, unless you have some need
to
lose or corrupt it. If you can't find a relevant post, tell us why and we
can repost it for you.

In your case you would repair your current data file, copy it, and open
it
in the other installation.
--
Russ Valentine
[MVP-Outlook]
Rob said:
i have yet to transfer my contacts from my old computer. i have an odd
issue
with my new system that needs to be resolved beforehand. but the
Outlook
techs from Dell and Microsoft that I have spoken to (probably 5 or 6)
recommend that I use the import/export feature, although they recognize
that
copying the default .pst file is another alternative.

just curious why this is. thanks for any input.
Click to expand...
Click to expand...
Click to expand...
 
thanks to everyone for the information. it is interesting that tech support
recommends import/export even though experts like yourselves understand the
possible issues as common knowledge.



Karl Timmermans said:
Did any of the tech's at either MS or Dell that you spoke with happen to
mention "WHY" they recommended "import/export" over opening the PST file in
the new installation? It absolutely boggles my mind why anyone would
recommend "import/export" as the preferred venue (am specifically referring
to PST2PST) other than it being a "textbook" response. Have yet to find
anything on or have anyone provide an explanation as to why PST2PST
import/export would be a better or preferred approach. Given the nature and
focus of our products - this is a topic that is more than just a passing
interest and, in fact, we highly recommend "against" ANY kind of
import/export, including using our own products, if the <sole> purpose is to
move from one installation to another - just absolutely not necessary.

Aside from all else, we've had to deal with "imported/exported" data from
customers on more than one occasion and have run across all kinds of
"anomalies" with the underlying data (or as might otherwise be referred to
in polite company as "undocumented features" making a given issue look like
it's the "other" program's problem).

More to point to your exact question "how does the import/export function
potentially corrupt files?" - it's hard enough to get all the info as to
what or how Outlook is "supposed" to do things when everything works
"correctly" let alone try and document all the ways that things can get
screwed up across multiple versions of Outlook particularly when the
internal processes that Outlook uses don't always seem to be the same as
those provided to the development community.

Karl
___________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
http://www.contactgenie.com


Rob said:
i did casually puruse this group but most replys to individuals that asked
about import/export were "this question is answered countless times every
day" followed by several links.

my interest is more about "how" does it corrupt.


Russ Valentine said:
With a casual perusal of this group you would quickly learn why you never
use import and export to transfer Outlook data, unless you have some need
to
lose or corrupt it. If you can't find a relevant post, tell us why and we
can repost it for you.

In your case you would repair your current data file, copy it, and open
it
in the other installation.
--
Russ Valentine
[MVP-Outlook]
i have yet to transfer my contacts from my old computer. i have an odd
issue
with my new system that needs to be resolved beforehand. but the
Outlook
techs from Dell and Microsoft that I have spoken to (probably 5 or 6)
recommend that I use the import/export feature, although they recognize
that
copying the default .pst file is another alternative.

just curious why this is. thanks for any input.
Click to expand...
Click to expand...
Click to expand...
 
It is the difference between reading a script and having to deal with the consequences of folks who listen to the script being read.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

thanks to everyone for the information. it is interesting that tech support
recommends import/export even though experts like yourselves understand the
possible issues as common knowledge.



Karl Timmermans said:
Did any of the tech's at either MS or Dell that you spoke with happen to
mention "WHY" they recommended "import/export" over opening the PST file in
the new installation? It absolutely boggles my mind why anyone would
recommend "import/export" as the preferred venue (am specifically referring
to PST2PST) other than it being a "textbook" response. Have yet to find
anything on or have anyone provide an explanation as to why PST2PST
import/export would be a better or preferred approach. Given the nature and
focus of our products - this is a topic that is more than just a passing
interest and, in fact, we highly recommend "against" ANY kind of
import/export, including using our own products, if the <sole> purpose is to
move from one installation to another - just absolutely not necessary.

Aside from all else, we've had to deal with "imported/exported" data from
customers on more than one occasion and have run across all kinds of
"anomalies" with the underlying data (or as might otherwise be referred to
in polite company as "undocumented features" making a given issue look like
it's the "other" program's problem).

More to point to your exact question "how does the import/export function
potentially corrupt files?" - it's hard enough to get all the info as to
what or how Outlook is "supposed" to do things when everything works
"correctly" let alone try and document all the ways that things can get
screwed up across multiple versions of Outlook particularly when the
internal processes that Outlook uses don't always seem to be the same as
those provided to the development community.

Karl
___________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
http://www.contactgenie.com


Rob said:
i did casually puruse this group but most replys to individuals that asked
about import/export were "this question is answered countless times every
day" followed by several links.

my interest is more about "how" does it corrupt.


Russ Valentine said:
With a casual perusal of this group you would quickly learn why you never
use import and export to transfer Outlook data, unless you have some need
to
lose or corrupt it. If you can't find a relevant post, tell us why and we
can repost it for you.

In your case you would repair your current data file, copy it, and open
it
in the other installation.
--
Russ Valentine
[MVP-Outlook]
i have yet to transfer my contacts from my old computer. i have an odd
issue
with my new system that needs to be resolved beforehand. but the
Outlook
techs from Dell and Microsoft that I have spoken to (probably 5 or 6)
recommend that I use the import/export feature, although they recognize
that
copying the default .pst file is another alternative.

just curious why this is. thanks for any input.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top