How to convert Word97/VBA .dot to Word2007/VBA .dotm ?

[elwook]

Hello everybody,

I have to migrate a Word97/VBA project to a Word2007/VBA environment.
This project is mainly a .dot file which contains 40 VBA functions/subs
including 10 which are exposed as macro, reachable from a custom
toolbar.

So, what should I do to ensure all will work fine, and without to forgot
anything ? Is there a verification tool around, something which convert
from W97 to W2K7 ?

At this point, trying to look around some minutes, I've just double-
clicked the original .dot (which comes from Word 97) : as result,
appearence of the document is OK, but the first piece of code which is
supposed to save standard toolbars (to restore them at the end of the
session), hide them and show the custom one doesn't seem to have any
effect, since I've the Word 2007 standard document's toolbar and the big
panel at top of the user-interface... So, I've the feeling, the try and
see is not the right method : it would be better to use a tool which
scan all the code and point the problematic lines.

In some words, I'm looking for the easiest way

 

[Cindy M.]

Hi Elwook,

I just finished a project bringing some five templates into Word 2007... I
know of no tool that will do this for you. If you're unfamiliar with Word
2007, then "try and see" is how it's going to have to be. Or hire someone
with experience that knows what needs to be done.

As far as the file format goes, you open the template in the new version
then save it as *.dotm.

Any toolbars defined in or by the template should appear in the Add-ins tab
of the Ribbon. If you don't like that, then you'll have to learn how to
create and incorporate RibbonXML.

In general, code should continue to work as before, although coming from
Word 97 there may be some major differences in some of the functionality
that will require adjustments (mail merge, tables and revisions (track
changes) are things that come to mind that have been re-worked in a big way
over the last ten years).

It would be important for you (or the person responsible for the template
(s)) to have a thorough understanding of how Word's functionality has
evolved during the past 10 years, so that your template can take advantage
of these things. For example, content controls or building blocks might be
an advantage.

I have to migrate a Word97/VBA project to a Word2007/VBA environment.
This project is mainly a .dot file which contains 40 VBA functions/subs
including 10 which are exposed as macro, reachable from a custom
toolbar.

So, what should I do to ensure all will work fine, and without to forgot
anything ? Is there a verification tool around, something which convert
from W97 to W2K7 ?

At this point, trying to look around some minutes, I've just double-
clicked the original .dot (which comes from Word 97) : as result,
appearence of the document is OK, but the first piece of code which is
supposed to save standard toolbars (to restore them at the end of the
session), hide them and show the custom one doesn't seem to have any
effect, since I've the Word 2007 standard document's toolbar and the big
panel at top of the user-interface... So, I've the feeling, the try and
see is not the right method : it would be better to use a tool which
scan all the code and point the problematic lines.

In some words, I'm looking for the easiest way

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail

 

[Graham Mayor]

To what extent you will have to modify the code will rather depend on what
it does. The simplest plan is to use the dot template in Word 2007, test the
macros and see what works. .

There are no toolbars in Word 2007, so what you will have available will be
on the add-ins tab. Any code designed to handle toolbars is not likely to be
of further use. The rest may not require conversion

I cannot think of an easier way than to 'suck it and see'.

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

 

[elwook]

To what extent you will have to modify the code will rather depend on what
it does. The simplest plan is to use the dot template in Word 2007, test the
macros and see what works. .

There are no toolbars in Word 2007, so what you will have available will be
on the add-ins tab. Any code designed to handle toolbars is not likely to be
of further use. The rest may not require conversion

I cannot think of an easier way than to 'suck it and see'.

Thanks, Graham. Effectively, just visited your rich site and see your
page at http://www.gmayor.com/Toolbars_in_word_2007.htm which talk about
this toolbar topic.

Well, so if I understand, ther's not any way to manage the user-
interface as we want, for the purpose to get a smart look n' feel for a
specific Word based application... Not very cool from Microsoft here :-(

I wonder if the best way wouldn't be to go through Word automation from
an external VB6 tool.

However, replying to your question about what my macros do : they manage
the life of a multi documents project with a final process which
concatenate them in a single long document with sections ; also, ther're
some macro about statistics, proprietary meta info saved in a .ini file,
acces to every document through quick lists (combo-box) in the custom
toolbar, etc.

 

[Graham Mayor]

Love it or loathe it, Word 2007 was a complete re-design as far as the user
interface was concerned.

If you want to create a ribbon for your project to replace the toolbar
function of the old template, then you can still do that -
http://gregmaxey.mvps.org/Customize_Ribbon.htm

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

 

[elwook]

Love it or loathe it, Word 2007 was a complete re-design as far as the user
interface was concerned.

If you want to create a ribbon for your project to replace the toolbar
function of the old template, then you can still do that -
http://gregmaxey.mvps.org/Customize_Ribbon.htm

Thanks a lot for this link, Graham. I'll study it deeply...

However and because I need to work using this application awaiting time
I'll migrate it toward Word 2007, is there a way to install Word 97
beside Word 2007 w/o conflict ?

 

[Graham Mayor]

Yes, you can have both. They use different folder locations, but they do
share some registry entries - see
http://www.gmayor.com/Toolbars_in_word_2007.htm which explains how to
overcome that problem.

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

 

[elwook]

Yes, you can have both. They use different folder locations, but they do
share some registry entries - see
http://www.gmayor.com/Toolbars_in_word_2007.htm which explains how to
overcome that problem.

It would be nice to have both Word 97 and Word 2007 on same Windows, but
the link you gave me is about toolbars, not dual installation : surely a
copy/paste mistake ;o)

Could you give me the right link to manage install of both 97 and 2007,
please ?

 

[Graham Mayor]

Have you read it? Don't judge what is on a web page by the url filename of
the page.

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

 

[elwook]

Have you read it? Don't judge what is on a web page by the url filename of
the page.

You're right : I was a little bit in urgency at time of my last
message... So, I'll take time to understand the interactions...

However, in the same time, I've found an alternative way which is maybe
not very clear about license, but acceptable in my case, just because
I've the official Office 97 Pro CD with license beside.

Well, the solution is to use what is called a portable release of Office
97... I've just copied the files in a directory and all stuffs about
registry, ini and temporary file are all done in this directory.

This way, my full Office 2007 is not disturbed at all and the macros of
my application seems to works (not tested deeply), but from what I've
seen it sounds right.

Also, this way allow me to copie this portable release in an USB key for
the purpose to be able to run my appli and show the multidoc project I
told about on any PC, for the time I've something to show Nice !