![]() |
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
| Tags: modules, repost, vanish, vbaprojectotm |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
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 |
| Ads |
|
#2
|
|||
|
|||
|
Ken wrote:
I'm reposting this query from 2 weeks ago, because it's a very vexing problem that I can't seem to solve. Perhaps asking in the programming newsgroup news://msnews.microsoft.com/microsof...ok.program_vba would be more appropriate, and that's where I set the followup. -- Brian Tillman |
|
#3
|
|||
|
|||
|
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 |
|
#4
|
|||
|
|||
|
Sue:
Tried that, and the problem still exists. Do you have any other suggestions? Thanks, and Happy New Year! "Sue Mosher [MVP-Outlook]" wrote in message ... 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 |
|
#5
|
|||
|
|||
|
You mean the problem recurred after you imported the code into the new project file? I have no other suggestions.
-- 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 ... Tried that, and the problem still exists. Do you have any other suggestions? "Sue Mosher [MVP-Outlook]" wrote in message ... 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. "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 |
|
#6
|
|||
|
|||
|
I'm more or less resigned to having to re-import the code every now and
again. BUT, the current problem is that not only is the code gone, but all of the options in the "File" menu or the VBA environment are greyed out. I've shut down everything, re-booted, but no progress. What do you make of THAT? Thanks. Ken "Sue Mosher [MVP-Outlook]" wrote in message ... 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 |
|
#7
|
|||
|
|||
|
Did you check Help | About MIcrosoft Outlook | Disabled Items?
-- 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 more or less resigned to having to re-import the code every now and again. BUT, the current problem is that not only is the code gone, but all of the options in the "File" menu or the VBA environment are greyed out. I've shut down everything, re-booted, but no progress. |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| VbaProject.OTM modules missing on opening OL2003 | Ken | Outlook - General Queries | 0 | December 7th 06 12:48 PM |
| large VBAProject.otm; performance considerations? | Bob | Outlook and VBA | 2 | May 26th 06 10:08 PM |
| Outlook 2003: Macro field is empty .. vbaproject.otm not recognized | Kemal Balioglu | Outlook and VBA | 2 | May 26th 06 05:45 PM |
| VBAProject.otm not read anymore | Dan | Outlook and VBA | 3 | February 21st 06 06:21 PM |
| Can't find the VbaProject.OTM file :( | yonina | Outlook and VBA | 2 | February 2nd 06 05:51 PM |