Office2003 and XP

[a]

Hi,
I have a Office 2003 and an XP system.
Is it possible to develop VBA for Word2000?
Word2003 is for .NET, right?
Thanks

 

[Cindy M -WordMVP-]

Hi A,

I have a Office 2003 and an XP system.
Is it possible to develop VBA for Word2000?
Word2003 is for .NET, right?

No, Word 2003's native programming language is still VBA.
As is the new version still in beta, Word 2007.

All versions of Word can be automated using .NET, but none
are "just for .NET". Word 2003 has some extras in it that
make it more interesting for .NET, is all.

Theoretically, you could write code in Word 2003 that will
run under Word 2000, but there are two possible "gotchas"

1. (Obvious) Word 2003 has functionality not availble in
2000. Anything you use that's not in 2000's VBA (or works
differently) will cause errors.

2. When you write code against the object model, the VBA
project registers which version of the library was used.
One sees this in the VB Editor, under Tools/References. For
Word 2003 there will be a reference to the Word 11.0 type
library. When such a project is loaded in an earlier
version of Word, theoretically Word will link to the
closest library version available. In practise, this
doesn't always work automatically, and the biggest
difficulties are usually with Word 2000. The user can,
however, set the reference manually.

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

 

[a]

Hi A,

No, Word 2003's native programming language is still VBA.
As is the new version still in beta, Word 2007.

All versions of Word can be automated using .NET, but none
are "just for .NET". Word 2003 has some extras in it that
make it more interesting for .NET, is all.

Theoretically, you could write code in Word 2003 that will
run under Word 2000, but there are two possible "gotchas"

1. (Obvious) Word 2003 has functionality not availble in
2000. Anything you use that's not in 2000's VBA (or works
differently) will cause errors.

2. When you write code against the object model, the VBA
project registers which version of the library was used.
One sees this in the VB Editor, under Tools/References. For
Word 2003 there will be a reference to the Word 11.0 type
library. When such a project is loaded in an earlier
version of Word, theoretically Word will link to the
closest library version available. In practise, this
doesn't always work automatically, and the biggest
difficulties are usually with Word 2000. The user can,
however, set the reference manually.

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


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

Thanks for you reply

Then, how can I guanrantee to use Word2003 to develop VBA that can run on
Word2000 without causing errors?

Thanks

 

[Doug Robbins - Word MVP]

You should always develop on the earliest version (Word 2000 in your case)
to ensure that you do not make use of any of the small number of additional
features that were added to the later versions

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP

 

[a]

If the target user uses Word2000 on XP platform, is it OK to develop my VBA
project on W2K or W98, Word2000?
Thanks

 

[Doug Robbins - Word MVP]

The platform is unlikely to be an issue. It is the version of the
application that is signficant.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP