I have a customer who exported his calendar into a pst a few weeks ago and
it's size was 55 Meg. Last week he exported his calendar (without removing
any apts) and the size now is 29 Meg. Previous pst files were also around 55
Meg, but his latest one is only 29 Meg. There doesn't appear to be any loss
of data (apts) in his calendar but we don't know why the file size dropped so
dramatically. Does anyone know the cause of this?
--
kaffelatte

kaffelatte wrote:

I have a customer who exported his calendar into a pst a few weeks
ago and it's size was 55 Meg. Last week he exported his calendar
(without removing any apts) and the size now is 29 Meg. Previous pst
files were also around 55 Meg, but his latest one is only 29 Meg.
There doesn't appear to be any loss of data (apts) in his calendar
but we don't know why the file size dropped so dramatically. Does
anyone know the cause of this?

I can think of a couple of causes but the file size you see is if very
little consequence. Don't think twice about it.

The more important issue is why your customer believes exporting to a PST is
ever a wise thing to de. Try to discourage that action, since it loses
data.
--
Brian Tillman

I disagree that the file size is inconsequential, but I'd be interested in
hearing what you think may have caused this anyway. The reason he exports to
a pst file is so he can take the file home and use it with his home system
without having to VPN in to access Outlook.
--
kaffelatte


"Brian Tillman" wrote:

kaffelatte wrote:

I have a customer who exported his calendar into a pst a few weeks
ago and it's size was 55 Meg. Last week he exported his calendar
(without removing any apts) and the size now is 29 Meg. Previous pst
files were also around 55 Meg, but his latest one is only 29 Meg.
There doesn't appear to be any loss of data (apts) in his calendar
but we don't know why the file size dropped so dramatically. Does
anyone know the cause of this?

I can think of a couple of causes but the file size you see is if very
little consequence. Don't think twice about it.

The more important issue is why your customer believes exporting to a PST is
ever a wise thing to de. Try to discourage that action, since it loses
data.
--
Brian Tillman

kaffelatte wrote:

I disagree that the file size is inconsequential, but I'd be
interested in hearing what you think may have caused this anyway.

Perhaps he deleted or archived some old appointments in which he was no
longer interested or autoarchived some data. Customers are notorious for
leaving out details of what they did because they believe them
inconsequential. Also, exporting loses data, so perhaps the reduction in
size is the result of that. As far as the file size being unimportant, a 55
MB PST is fairly small, as far as PSTs go, and that's why I say it's size is
of no concern.

The reason he exports to a pst file is so he can take the file home
and use it with his home system without having to VPN in to access
Outlook.

The WRONG thing to do. He should simply copy his original PST with Outlook
closed to the transport medium. Alternatively (if he wants only his
calendar), he should create a new PST with FileNewOutlook Data File, copy
the calendar to that new PST, then close that PST and with Outlook closed,
transfer that PST to the transport medium. On the destination machine, he
should open the PST with FileOpenOutlook Data File. He can then copy the
contents of that calendar to his default calendar or simply use it as-is as
a separate calendar folder.
--
Brian Tillman