I've seen that happen occasionally -- and almost always when a run-a-script rule was involved. THe exact cause of the problem is not known.

I'd suggest exporting all the code, shutting down Outlook, and renaming VbaProject.OTM. When you restart Outlook and re-enter the VBA environment, you can import all the code into the new project file that Outlook will create automatically. Hopefully, that one will be more stable.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Ken" wrote in message ...
I'm reposting this query from 2 weeks ago, because it's a very vexing
problem that I can't seem to solve. Any help would be greatly appreciated.

Thanks, and happy holidays!
----------------------------------------------------
For the second day in a row, on starting up OL2003, SP2, a script that I've
created is missing--as in totally vanished.

I created a rule that runs a script on receiving messages that have an
attachment. The script is located in a module within "Project1
(VbaProject.OTM)".

The structure is:
Project1(VbaProject.OTM)
Microsoft Office Objects
This Outlook Session
Modules
Module 1
Module 2 (Module 2 has the
script)

The Rule/Script works fine during the day. I shut down Outlook at the end
of the day. This morning, for the second day in a row, when I started up
OL, I got a error message that the script did not exist. When I opened up
the Visual Basic Editor, the only thing there was the Microsoft Office
Objects branch (containing the empty This Outlook Session). There was no
"Modules" branch, and thus no Module 1 or Module 2.

Since I run Norton GoBack, I restored to a few hours earlier, and got it
back.

Any ideas what might be going on?

(Virus protection is up-to-date, FWIW).

Many thanks.

Ken