large VBAProject.otm; performance considerations?

[Guest]

After some years of continually adding various processing chores to our
VBAProject.otm, I am concerned about Outlook's stability and performance.

Does anybody know if having lots of work performed in there can cause
problems with Outlook? We seem to have some strange problems sending mail
(items not leaving Outbox, etc.) and I can't help but think maybe the
"OnSend" events that are trapped (or whatever it is; I'm just the admin, not
programmer) might be contributing. There are other things, too.

I guess there are no specific questions here... I just wonder if anybody
knows whether too many tasks in that VBA file can cause problems with
Outlook. Isn't there another way to customize Outlook, such as using
add-ins, that would be better and safer? On my personal system, Outlook 2003
without any customization has ZERO problems like this.

We're Outlook 2003, Exchange Enterprise 2003.

thanks for your time,
bob

 

[Ken Slovak - [MVP - Outlook]]

Yes, a large VBA project can slow things down and the code can do various
things. COM addins are better solutions but if the code isn't written
correctly then no matter what vehicle you use you will have problems. My own
VBA project file is about 5 MB at this point, code I use to test and
prototype.

 

[Guest]

Thanks for the info. It does help.

Yes, a large VBA project can slow things down and the code can do various
things. COM addins are better solutions but if the code isn't written
correctly then no matter what vehicle you use you will have problems. My own
VBA project file is about 5 MB at this point, code I use to test and
prototype.