Thanks for trying to get me up to speed on this.
I made a fat finger error in that the last statement should have read, "were
NOT connected at the same time."
Thanks again.
Norman

"Brian Tillman" wrote in message
...
Norman wrote:

According to some posts:

Don't export your pst as a pst, it loses data?

Correct

Don't import a pst, it loses data?

Correct.

Is this function broken and unfixable?

While some would consider it broken, I doubt it will ever be "fixed"
because
there are better ways to transfer data from Outlook to Outlook. You don't
export and import a Word document from Word to Word. Likewise, you don't
export and import an Outlook-native file with Outlook. There are
situations
when exporting and importing are appropriate and when you understand the
limitations of those operations, they work perfectly, so in that sense,
nothing's broken. They're not suitable for "imaging" a pst, however, and
that's how most people try to use them.

Don't copy your pst to another machine, then connect with it because
it will create duplicates if the messages are still on the server?

Sometimes, yes.

Something about the messages being downloaded already isn't stored in
the pst.

Correct. Data about what server items have been downloaded already and
which have not, whether kept in the PST or elsewhere, is strictly Outlook
instance-specific and cannot be transferred between Outlook instances.

From long ago, you could run more than one machine against the same
pst as long as they both were connected at same time. Is that still
true?

I don't know if that's ever been true. As far as I know, PSTs have always
been able to be opened only by a single instance of Outlook at any one
time.
--
Brian Tillman