macro menu items no longer activated

[PeterQ]

hello Team,

I am using Outlook 2003 on an Exchange 2003 server. I am developing vba
macros and for the time being I use the vbaproject.otm macrofile to
store the macros.
However, for two users I detected that it had become impossible to
select a menu-item from the macro-submenu.

Clicking on "Macro's" or "Security" or "Visual Basic Editor" did not
activate anything at all !! No dialog, no other screen, just nothing
happened.

(Neither was the code in the ThisOutlookSession.cls file activated when
starting Outlook)

Please, does anyone know, what can be the cause of this and what should
be an appropiate solution ?
I would be very grateful.

Greetings,
Peter

 

[Sharad Naik]

May be VBA support was not installed on those computers.
Run Office 2003 set up program again on those computers and enable VBA
support.
To re-enable VBA, follow these steps:

1.. Run the Office Setup program again.
1.. Quit all programs.
2.. Double-click the Add/Remove Programs icon in the Microsoft Windows
Control Panel.
3.. Do one of the following:
a.. If you installed your Office program as part of Microsoft Office,
click Microsoft Office in the Currently installed programs box, and then
click the Change button.
b.. If you installed your Office program individually, click the name
of your program in the Currently installed programs box, and then click the
Change button.
2.. On the Features to install screen in the Setup program, click the plus
sign (+) next to Office Shared Features.
3.. Select Visual Basic for Applications, click the arrow next to your
selection, and then click Run from My Computer.

Sharad

 

[PeterQ]

hello Sharad,

Thank you very much for answering to my message.
I have tried to apply it right away.
However your solution does not apply to the problem.

In my case the menu items are enabled. I can click on them. But there is
no response to it.

Using the setup following your procedure the menu items are enabled or
disabled depending on whether VBA is selected or not.

I noticed that when the sysadmin reset the profile of a user that has
this problem, the problem was solved. But I surely am interested in what
the cause can be.

Perhaps you have another suggestion ?


Greetings,
Peter