moving from Office 2000 to 2003

[Doug Boufford]

Computer stolen, so time to upgrade from Office 2000 to 2003.
Installed Office 2003 & moved everything over from backups to equivalent
folders in 2003. The only problem in Word appears to be one template
that contains many vba macros. This template worked fine in Word 2000
(the day before installing 2003), but causes a crash in Word 2003.

Any hints about what to look for as I don't relish redoing all of the macros

TIA
Doug

 

[Jay Freedman]

Computer stolen, so time to upgrade from Office 2000 to 2003.
Installed Office 2003 & moved everything over from backups to equivalent
folders in 2003. The only problem in Word appears to be one template
that contains many vba macros. This template worked fine in Word 2000
(the day before installing 2003), but causes a crash in Word 2003.

Any hints about what to look for as I don't relish redoing all of the macros

TIA
Doug

Insufficient information...

What kind of crash? Does Word itself stop working, or is it just a
macro that stops? Is there an error message; if so, exactly what does
it say?

What are you doing at the time of the crash? Are you running a macro,
or just basing a document on the template? Or is the template a global
add-in (stored in the Startup folder)?

When the problem occurs, does the VBA editor open with a line of code
highlighted? If so, what is that line?

There are a number of other things to investigate if the answers to
these questions don't pinpoint the cause right away.

 

[Doug Boufford]

Insufficient information...

What kind of crash? Does Word itself stop working, or is it just a
macro that stops? Is there an error message; if so, exactly what does
it say?

I have disabled the template for now & Word will run fine.
When it is enabled, Word will open & the a message that (paraphrasing)
"Word has encountered an error and must close" and close it does!

What are you doing at the time of the crash? Are you running a macro,
or just basing a document on the template? Or is the template a global
add-in (stored in the Startup folder)?

Template (Doug.dot) is stored in the Startup folder. When it is enabled,
all I do is start Word& then receive the above error & Word closes. When
the template is disabled, Word runs fine, but obviously the macros from
that template are not available

When the problem occurs, does the VBA editor open with a line of code
highlighted? If so, what is that line?

NO - it does not open & no further error messages appear, other then
that noted above.

There are a number of other things to investigate if the answers to
these questions don't pinpoint the cause right away.

--
Regards,
Jay Freedman
Microsoft Word MVP
Email cannot be acknowledged; please post all follow-ups to the newsgroup so all may benefit.

Thanks
Doug

 

[Jay Freedman]

OK, the crash on startup with a global template points to the probability
that the template is damaged in some way so that Word isn't able to load it.
I'll suggest making a new copy of the template that you know works in Word
2000, and replace the one in 2003.

AutoExec, AutoNew and Document_New macros
(http://word.mvps.org/FAQs/MacrosVBA/DocumentEvents.htm) stored in a global
template should not be invoked, so I doubt the problem is associated with a
macro, but you can look at the template in Word 2000 to see if any of them
are present (or possibly an application event handling class,
http://word.mvps.org/faqs/macrosvba/AppClassEvents.htm).

 

[Doug Boufford]

Thanks for that Jay
The original template worked fine in Office 2000. I copied that template
from a Ghost BU & inserted it after Office 2003 was installed, so I
don't see how it might have gotten corrupted.
How do I make "a new copy of the template that you know works in Word

2000, and replace the one in 2003" ?

Many thanks
Doug

 

[Jay Freedman]

Sorry, I assumed you had restored the Word 2000 setup from backup and
tried it. I guess you can disregard that bit of advice. (Although you
might try extracting another copy from the Ghost backup to see if it
behaves the same.)

When you said you "disabled" the template, do you mean you moved it to
another folder? Try opening it as if it's a document, using the File >
Open dialog and navigating to the folder. Does it open OK? If so, open
the VBA editor, go into the Project pane (Ctrl+R if it isn't open
already), right-click each module in turn, and choose Export to File.
Then create a new empty template, right-click the new template's
project in the Project pane, and use the Import File item to load the
code into it. Save that template into the Startup folder and see if it
behaves better.

 

[Doug Boufford]

Jay
I restored the template from another backup & it seems to work fine.
Many thanks for your help
Doug

 

[Jay Freedman]

You're welcome. I'm glad it turned out all right.

Jay