A new phenomenon has shown itself with VBA Word 2003 on my machine. After using Rob Bovey's Version 4.4 code cleaner on a Word template, the auto macros in that template did not fire. Additionally, none of the procedures were visible in the macros window (Alt + F8); though they were present in the VBE.
This situation corrected itself when a new procedure was created in, and subsequently removed from the project in VBE.
Just in case someone else suffers from the same symptoms.
Unexposed procedures
-
- 5StarLounger
- Posts: 689
- Joined: 27 Jan 2010, 16:45
- Location: Ottawa, Ontario, Canada
Unexposed procedures
Last edited by Don Wells on 12 Feb 2010, 15:48, edited 2 times in total.
Regards
Don
Don
-
- Administrator
- Posts: 79042
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Unexposed procedures
Did you re-compile the code after running the code cleaner (Debug | Compile <project name>)?
Best wishes,
Hans
Hans
-
- 5StarLounger
- Posts: 689
- Joined: 27 Jan 2010, 16:45
- Location: Ottawa, Ontario, Canada
Re: Unexposed procedures
Yes. I also closed Word immediately after compiling.HansV wrote:Did you re-compile the code after running the code cleaner (Debug | Compile <project name>)?
Thanks for the response.
Regards
Don
Don
-
- PlutoniumLounger
- Posts: 15899
- Joined: 24 Jan 2010, 23:23
- Location: brings.slot.perky
Re: Unexposed procedures
Yup. I've seen this too, at most twice a year. I work (still) mainly in 2000.Don Wells wrote: Additionally, none of the procedures were visible in the macros window ...
The first time was unnerving.
I’ve been tidying the junk out of my shed for five years, and now can hardly get into the shed