Next Version Of Office

[vbnetdev]

Does anyone know if it will support automation like it does now in vba? Does
anone know if macros written now in Word or Excel will still continue to
function?

 

[Karl E. Peterson]

Does anyone know if it will support automation like it does now in
vba? Does anone know if macros written now in Word or Excel will
still continue to function?

Yes, with some "issues" surrounding UI apparently.

 

[vbnetdev]

Do you know of any white papers or other information I can read more about
this?

Thanks for your help

 

[Karl E. Peterson]

Do you know of any white papers or other information I can read more
about this?

Here's one:

http://www.betanews.com/article/New_UI_Highlights_Changes_in_Office_12/1126637423

More here:

http://www.google.com/search?q=vba+"office+12"

 

[Jay Freedman]

Here's one:

http://www.betanews.com/article/New_UI_Highlights_Changes_in_Office_12/1126637423

More here:

http://www.google.com/search?q=vba+"office+12"

Just be careful about the dates on the articles you read. A lot of the
ones you'll find on the web (including the betanews.com article) were
written in late 2005, shortly after the first "sneak previews" and
before even the first beta release. Much has changed since then,
including a lot of clarifications of early misstatements.

For example, an article from computerweekly.com that turns up in the
first page of the Google results dates from July 2005. It claims that
"documents saved in the new XML file format will not be able to run
macros or Office applications developed using VBA." This is extremely
misleading. The new file format has two distinct file types for each
Office app that supports VBA -- for Word there are .dotx and .dotm for
templates, and .docx and .docm for documents -- where the "x" version
won't *store* any macro code but the "m" version will. The macros can
*run* against either kind (once in memory, they're the same).

All of the old VBA I've tried works well, but I don't generally do
anything that modifies menus or toolbars in code -- since there aren't
any to modify, that code won't work, and you'll have to learn RibbonX.
There are also new bits in the object model to deal with new features.

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

 

[Cindy M -WordMVP-]

Hi Jay,

All of the old VBA I've tried works well, but I don't generally do
anything that modifies menus or toolbars in code -- since there aren't
any to modify, that code won't work, and you'll have to learn RibbonX.

Actually, that's not correct. The code will, indeed, continue to run. It
will (should) work with the new UI area to which toolbar customizations
have been relegated. And code which manipulates context menus will
(should) continue to work as ever.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
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

 

[Jay Freedman]

Hi Jay,

Actually, that's not correct. The code will, indeed, continue to run.
It will (should) work with the new UI area to which toolbar
customizations have been relegated. And code which manipulates
context menus will (should) continue to work as ever.

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


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

Thanks for the correction, Cindy. As I said, I don't do that kind of
customization in my own templates, so it doesn't show up on my radar.

And I'm not sure I consider stuff relegated to the legacy UI area to be
"working" customization. It's more like "we couldn't fit any cargo area into
your new truck, so we gave you a trailer hitch."

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