vba for outlook addin disabled

  • Thread starter Thread starter ActiveNZ_Adrian
  • Start date Start date
A

ActiveNZ_Adrian

I have recently installed Outlook 2003 in our office as
part of a SBS2003 installation, and frequently on start-
up, it comes up with the message that the module vba for
outlook addin caused a serious error last time Outlook was
run and has been disabled. However, at no stage had
Outlook crashed, or come up with any error messages
regarding this 'serious error'.

I can re-enable it, according to the instructions given,
and the macros run fine, but every now and again, it will
disable vba again. The macros are very straightforward and
ran fine on Outlook 2000 (our previous version), and once
the addin is enabled, run fine in 2003. This is happening
on more than one computer, and seeing as we intend to use
macros extensively in the future, is a real problem. I saw
another post on a similar problem, but that hadn't been
resolved. Is this a known problem with Outlook 2003?

Adrian
 
VBA has been known to flake out in earlier versions, too, but it's
relatively rare. You might have a corrupted VbaProject.otm file. Export all
modules, exit Outlook, rename that file, then restart Outlook. You can
import your modules into a clean .otm file that Outlook will create
automatically.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers




I have recently installed Outlook 2003 in our office as
part of a SBS2003 installation, and frequently on start-
up, it comes up with the message that the module vba for
outlook addin caused a serious error last time Outlook was
run and has been disabled. However, at no stage had
Outlook crashed, or come up with any error messages
regarding this 'serious error'.

I can re-enable it, according to the instructions given,
and the macros run fine, but every now and again, it will
disable vba again. The macros are very straightforward and
ran fine on Outlook 2000 (our previous version), and once
the addin is enabled, run fine in 2003. This is happening
on more than one computer, and seeing as we intend to use
macros extensively in the future, is a real problem. I saw
another post on a similar problem, but that hadn't been
resolved. Is this a known problem with Outlook 2003?

Adrian
 
Back
Top