Hello,

I've got a computer that was a new Windows XP installation. We moved the
clients files over via Microsoft's Files and Settings Transfer Wizard.
The old and new machine uses Outlook from the Office 2000 installation
as opposed to the newest version of Office (2003).

On the old machine, Outlook 2000 (NOT outlook 2003) would periodically
"unexpectedly quit". The old computer was slow and old so the client
upgraded and once the files were transferred the unexpected crashes
started happening on the new computer as well.

I now suspect that there's some sort of corruption in the Account files
for Outlook 2000. My solution is to export the data (address book, email
messages, etc.) and then delete the account and create a whole new one
from scratch. This is going to entail quite a bit of work and I was
hoping someone else on this newsgroup had experienced something similar
to this before and could stop me before I get too far into this solution
with a better alternative.

Any ideas?

Thanks,
Denny

The most common cause for Office program's exiting immediately without
warning is a bug with the SR1 patch. This MS KB article may help:
http://support.microsoft.com/default...;EN-US;Q255503

--
Russ Valentine
[MVP-Outlook]
"DadMan" wrote in message
...
Hello,

I've got a computer that was a new Windows XP installation. We moved the
clients files over via Microsoft's Files and Settings Transfer Wizard. The
old and new machine uses Outlook from the Office 2000 installation as
opposed to the newest version of Office (2003).

On the old machine, Outlook 2000 (NOT outlook 2003) would periodically
"unexpectedly quit". The old computer was slow and old so the client
upgraded and once the files were transferred the unexpected crashes
started happening on the new computer as well.

I now suspect that there's some sort of corruption in the Account files
for Outlook 2000. My solution is to export the data (address book, email
messages, etc.) and then delete the account and create a whole new one
from scratch. This is going to entail quite a bit of work and I was
hoping someone else on this newsgroup had experienced something similar to
this before and could stop me before I get too far into this solution with
a better alternative.

Any ideas?

Thanks,
Denny