Testing a template macro

G

GrannyM

We recently updated from Word 97 to Word 2003 - big jump!

Our office uses templates with macros attached. In Word 97, when we wanted
to test a problem, we could open the template, open the vba editor, set a
breakpoint in the code, go back to Word, and run the template (File, New ...)
which created a new document based on the template. In the project window in
VBA Editor it showed PROJECT(templatename) and PROJECT(Document#). The code
was with the master template, not the newly created doucment, and so it would
stop at the breakpoint so that we could step through the code and find the
problem in the code without actually changing the original template.

However, I'm finding that in 2003 when you run the template, it doesn't
access the original that is already open. It opens a new copy of the project
in vba so that it doesn't stop at the breakpoint I've set. The project
window shows 2 projects, both with the same templatename.

Is there some setting that needs to be set to fix this, or is this just
something we're going to have to learn to live with?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top