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.

Re: how does the import/export function potentially corrupt files?... by Diane

Diane
Thu Apr 17 07:28:15 PDT 2008

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.



--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:
dailytips-subscribe-request@lists.outlooktips.net

Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:
EMO-NEWSLETTER-SUBSCRIBE-REQUEST@PEACH.EASE.LSOFT.COM

** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **


"Rob" <Rob@discussions.microsoft.com> wrote in message
news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
> 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.


Re: how does the import/export function potentially corrupt files?... by Russ

Russ
Thu Apr 17 08:31:30 PDT 2008

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" <Rob@discussions.microsoft.com> wrote in message
news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
>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.


Re: how does the import/export function potentially corrupt files? by Rob

Rob
Thu Apr 17 07:39:00 PDT 2008

i have Outlook 2003 with XP on my old computer and OL 2007 on my new computer
which runs Vista.

"Diane Poremsky {MVP}" wrote:

> 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.
>
>
>
> --
> Diane Poremsky [MVP - Outlook]
> Author, Teach Yourself Outlook 2003 in 24 Hours
> Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
> Outlook 2007: http://www.slipstick.com/outlook/ol2007/
>
> Outlook Tips by email:
> dailytips-subscribe-request@lists.outlooktips.net
>
> Outlook Tips: http://www.outlook-tips.net/
> Outlook & Exchange Solutions Center: http://www.slipstick.com
> Subscribe to Exchange Messaging Outlook newsletter:
> EMO-NEWSLETTER-SUBSCRIBE-REQUEST@PEACH.EASE.LSOFT.COM
>
> ** Please include your Outlook version, Account type, and Windows Version
> when requesting assistance **
>
>
> "Rob" <Rob@discussions.microsoft.com> wrote in message
> news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
> > 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.
>

Re: how does the import/export function potentially corrupt files? by Rob

Rob
Thu Apr 17 07:43:01 PDT 2008

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 [MVP-Outlook]" wrote:

> 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" <Rob@discussions.microsoft.com> wrote in message
> news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
> >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.
>

Re: how does the import/export function potentially corrupt files? by Gordon

Gordon
Thu Apr 17 08:13:56 PDT 2008

"Rob" <Rob@discussions.microsoft.com> wrote in message
news:FCE7ABE9-4335-49FE-8D76-DD62C8D4E857@microsoft.com...
>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.
>

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)


Re: how does the import/export function potentially corrupt files? by Karl

Karl
Thu Apr 17 08:52:29 PDT 2008

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" <Rob@discussions.microsoft.com> wrote in message
news:FCE7ABE9-4335-49FE-8D76-DD62C8D4E857@microsoft.com...
>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 [MVP-Outlook]" wrote:
>
>> 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" <Rob@discussions.microsoft.com> wrote in message
>> news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
>> >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.
>>



Re: how does the import/export function potentially corrupt files? by Rob

Rob
Thu Apr 17 10:08:00 PDT 2008

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" wrote:

> 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" <Rob@discussions.microsoft.com> wrote in message
> news:FCE7ABE9-4335-49FE-8D76-DD62C8D4E857@microsoft.com...
> >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 [MVP-Outlook]" wrote:
> >
> >> 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" <Rob@discussions.microsoft.com> wrote in message
> >> news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
> >> >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.
> >>
>
>
>

Re: how does the import/export function potentially corrupt files? by Milly

Milly
Thu Apr 17 21:43:54 PDT 2008

It is the difference between reading a script and having to deal with =
the consequences of folks who listen to the script being read.

--=20
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. =20

"Rob" <Rob@discussions.microsoft.com> wrote in message =
news:EA8EB97F-DD94-4E99-B70D-765B5E7803EA@microsoft.com...
thanks to everyone for the information. it is interesting that tech =
support=20
recommends import/export even though experts like yourselves understand =
the=20
possible issues as common knowledge.



"Karl Timmermans" wrote:

> Did any of the tech's at either MS or Dell that you spoke with happen =
to=20
> mention "WHY" they recommended "import/export" over opening the PST =
file in=20
> the new installation? It absolutely boggles my mind why anyone would=20
> recommend "import/export" as the preferred venue (am specifically =
referring=20
> to PST2PST) other than it being a "textbook" response. Have yet to =
find=20
> anything on or have anyone provide an explanation as to why PST2PST=20
> import/export would be a better or preferred approach. Given the =
nature and=20
> focus of our products - this is a topic that is more than just a =
passing=20
> interest and, in fact, we highly recommend "against" ANY kind of=20
> import/export, including using our own products, if the <sole> purpose =
is to=20
> move from one installation to another - just absolutely not necessary.
>=20
> Aside from all else, we've had to deal with "imported/exported" data =
from=20
> customers on more than one occasion and have run across all kinds of=20
> "anomalies" with the underlying data (or as might otherwise be =
referred to=20
> in polite company as "undocumented features" making a given issue look =
like=20
> it's the "other" program's problem).
>=20
> More to point to your exact question "how does the import/export =
function=20
> potentially corrupt files?" - it's hard enough to get all the info as =
to=20
> what or how Outlook is "supposed" to do things when everything works=20
> "correctly" let alone try and document all the ways that things can =
get=20
> screwed up across multiple versions of Outlook particularly when the=20
> internal processes that Outlook uses don't always seem to be the same =
as=20
> those provided to the development community.
>=20
> 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
>=20
>=20
> "Rob" <Rob@discussions.microsoft.com> wrote in message=20
> news:FCE7ABE9-4335-49FE-8D76-DD62C8D4E857@microsoft.com...
> >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 [MVP-Outlook]" wrote:
> >
> >> 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=20
> >> 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=20
> >> it
> >> in the other installation.
> >> --=20
> >> Russ Valentine
> >> [MVP-Outlook]
> >> "Rob" <Rob@discussions.microsoft.com> wrote in message
> >> news:B9E9EFE7-B3EE-46DB-BC84-E9B697F1AFD7@microsoft.com...
> >> >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.
> >>=20
>=20
>=20
>