Re: Outlook 2k3: VBA will not start

What do I use to kick off this sub? I put it in the code window as you
suggested, but not being associated with an event, like startup, how do I run
the sub?
Graham

"Sue Mosher [MVP-Outlook]" wrote:

As I said, try running a separate subroutine. That will help you know whether the problem is with VBA in general or with the Startup event handler.

--
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

"Graham Anderson" <GrahamAnderson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:24100406-1335-4418-A28F-B0A0B3F89D5D@xxxxxxxxxxxxxxxx
My code is that simple, just one MsgBox statement. I have put it to run at
Application Startup. Where can I place it to be simpler?
Graham

"Sue Mosher [MVP-Outlook]" wrote:

It should run, but you should also be testing basic VBA functionality with a simpler procedure, e.g.

Sub Hello()
MsgBox "Hello World"
End Sub

Another thing you can try is to export your code if you want to keep it, shut down Outlook, rename the VbaProject.otm file, then restart Outlook. That will create a new VbaProject.otm file to store the code.


"Graham Anderson" <GrahamAnderson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6C416A2C-24D5-4A02-B02B-5D64EF1FE0DC@xxxxxxxxxxxxxxxx
I shut down the computer and then started again. When I started Outlook, none
of the VBA kicked in. It is just a simple MsgBox in the Application_Startup
sub. Please confirm I don't need to compile it or anything. The code sits in
the code window (Alt+F11) and is still there when I restart. So it should run
shouldn't it?
Graham

"Sue Mosher [MVP-Outlook]" wrote:

Another possible cause of these symptoms is that Outlook is never really shutting down between sessions. If you restart Windows, do you get the same results?

"Graham Anderson" <Graham Anderson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:741D3AAE-9254-43AE-9940-3A4DDB5BFF1D@xxxxxxxxxxxxxxxx
I just found I had this same problem and I checked the Help..About.. and
nothing was disabled. My problem is that VBA doesn't seem to get started or
be recognized. I have attempted to re-install the Shared VBA part of MS
Office, as directed in the Help for Outlook, but it doesn't seem to want to
install (remains a white cabinet, not a grey one). Any thoughts?
Graham

"Sue Mosher [MVP-Outlook]" wrote:

Did you check Help | About Microsoft Office Outlook | Disabled Items?

"Chuck Tremain" <ChuckTremain@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E552CC6F-E0DB-47F5-9C4A-B70F4FF13657@xxxxxxxxxxxxxxxx
I have two PCS: at work: Win/2000 running Office/2000... at home: Win/XP-Pro
running Office/2003. My problem is with my home Office/2003 and specifically
Outlook/2003.

I have written a visual basic macro on my "work" PC for Outlook/2000.
Please don't tell me how stupid I was... but I assumed that Outlook/2003
would handle the Outlook/2000 VbaProject.OTM in much the same way Word
2000/2003 accesses Normal.dot. Outlook/2003 doesn't.

This is what I did: I copied the Outlook/2000 VbaProject.OTM into the
Outlook/2003 directory at C:\Documents and Settings\Chuck\Application
Data\Microsoft\Outlook. Outlook/2003 started-up just fine. I accessed the
visual basic code without problem. I exited Outlook/2003 without any errors.

However, when I came back to my Outlook/2003 module and started-up the
visual basic editor - nothing happened. I click on the option Tools --->
Macro ---> Visual Basic Editor and nothing happens. Period. Alt+F8 is dead
and Alt+F11 does nothing, either.

I changed the name of VbaProject.OTM to VbaProject.SAVOTM, clicked on the VB
Editor, and still nothing happens.

All other options of Outlook/2003 work just fine... it is just that I cannot
start the VB editor, nor do I get the Tools ---> Macro ---> Macros dialogue
box.

How do I fix it????
If I need to Add/Remove Outlook and then do a complete reinstall, what do I
need to do to preserve my existing folders/contacts/etc????

By the way I did run the "Detect and Repair" option off of the CD. There
was no change in the way the VB Editor responded.

Many thanks!

Chuck Tremain

--
Chuck Tremain




.

Relevant Pages

  • Re: determine encryption?
    ... It is very small and is the only one: Remember Outlook 2002 VBA not Outlook Express.: ... Public Sub TestMail ... This email and Outlook 2002 VBA are not on good terms. ... If I don't this encryption breaks VBA and so my script rule. ...
    (microsoft.public.security)
  • Re: Outlook 2k3: VBA will not start
    ... It should run, but you should also be testing basic VBA functionality with a simpler procedure, e.g. ... Sub Hello ... Another thing you can try is to export your code if you want to keep it, shut down Outlook, rename the VbaProject.otm file, then restart Outlook. ... It is just a simple MsgBox in the Application_Startup ...
    (microsoft.public.office.developer.outlook.vba)
  • Re: COM Addin Problem after Update to Outlook 2003
    ... It worked with Outlook 2000 and XP, ... Only the Addin wasn't loaded. ... > Private Sub IDTExtensibility2_OnAddInsUpdateAs Variant) ... > On Error GoTo ErrHandler ...
    (microsoft.public.outlook)
  • Re: COM Addin Problem after Update to Outlook 2003
    ... It worked with Outlook 2000 and XP, ... Only the Addin wasn't loaded. ... > Private Sub IDTExtensibility2_OnAddInsUpdateAs Variant) ... > On Error GoTo ErrHandler ...
    (microsoft.public.outlook.program_addins)
  • AttachmentAdd Event
    ... I have copied the code in to the project as explained and closed the VBA ... In Microsoft Visual Basic Scripting Edition in an Outlook ... Private Sub newItem_AttachmentAdd(ByVal newAttachment As Attachment) ...
    (microsoft.public.outlook.program_vba)