New VBA features in 2002?

[Sam]

Hi all

Is there a reference source that lists any/all new
objects/methods/properties in VBA for Office 2002? I looked on the MS Office
Developer pages and there seems to be a very clear list (hopefully complete)
for 2003, but the 2002 section just seems to provide an alphabetical list
without specifying what's new and what's not.

Thanks for any guidance...

 

[Steve Rindsberg]

Hi all

Is there a reference source that lists any/all new
objects/methods/properties in VBA for Office 2002? I looked on the MS Office
Developer pages and there seems to be a very clear list (hopefully complete)
for 2003, but the 2002 section just seems to provide an alphabetical list
without specifying what's new and what's not.

The VBA help files for at least Word and PPT have a What's New section that
describes new methods/objects/properties.

 

[Sam]

Hi Steve

Thanks - are those help files available on the MS website? I don't have
2002 just 2003, but we're upgrading from 2000 so I need to know what the
cumulative changes are for 2002 and 2003.

TIA

Sam

 

[Steve Rindsberg]

Hi Steve

Thanks - are those help files available on the MS website? I don't have
2002 just 2003, but we're upgrading from 2000 so I need to know what the
cumulative changes are for 2002 and 2003.

I don't know about the help files but it looks like you can find what you need like
so:

http://msdn.microsoft.com/library/default.asp

Open "Office Solution Development"
Open "Microsoft Office XP"
Open "Office XP" (I don't make it up, I just report it)
Open the app you're interested in

There should be a "What's New" item under that. If not, I guess nuttin's knew? ;-)

 

[Howard Kaikow]

Hi Steve

Thanks - are those help files available on the MS website? I don't have
2002 just 2003, but we're upgrading from 2000 so I need to know what the
cumulative changes are for 2002 and 2003.

The changes that get listed in "What's New" are little more than a list of
added properties and methods, and new args for extant properties and
methods.

The stuff one needs to worry about when migrating code from an older version
to a newer version is "what got broken" in the new version, or "what will no
longer work" in the new version. In to determine these, one needs to test
the code in the new version. If one is lucky, there'll be no unpleasant
surprises.

Any known problems, if you are lucky, might be documented in KB articles,
but not in What's New.

 

[Sam]

Thanks Steve and Howard. We're going to be testing all our code thoroughly
but in addition I was looking for reference that would give us ideas for
possible improvements using new stuff. I got a link in the Office Developer
thread:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbaof10/html/ofconWhatsNew.asp

 

[Howard Kaikow]

Thanks Steve and Howard. We're going to be testing all our code thoroughly
but in addition I was looking for reference that would give us ideas for
possible improvements using new stuff. I got a link in the Office Developer
thread:

First, cross your fingers, eyes, toes, etc, and hope that all your code
migrates without errors.
Then, you can uncross your fingers, eyes, toes, etc. and look for ways to
improve things.

Moving from Office 97 to Office 2000, there are indeed opportunities for
significant improvements.

Moving from Office 2000 to later versions, the opportunities are less so.
Dependfs on which Office app is of interest.