Mircosoft's future strategy regarding VBA?

[Julian Turner]

Hi

I am a lawyer used to working with long complex word documents,
containing multiple outline numbering lists etc.

In my work I have developed a high level of proficiency with VBA (as
well as automating Word using ActiveX and JavaScript), and have
created a large library of VB routines to help me manage documents.

I am interested in understanding what Microsoft's long term strategy
for VBA is, and would be interested in hearing any views.

I believe that VBA in 2007 is little different to VBA in 2003, and
whilst powerful and comprehensive already, there are no obvious new
features or controls available for UserForms, and worse, the flexible
level of customisation for menus has been supplemented by the more
rigid and complex Ribbon.

In an ideal world, especially, I would like to be able to create,
using VBA, a dockable custom TaskPane to hold all my VB routines
(rather than a modeless UserForm or custom tool bar in the Add-In
Ribbon), but I note that to be able to do this, it seems I need to
master COM based Add-Ins and aquire C# / VB.NET skills as well as a
professional version of Visual Studio.

Does all of this point to Microsoft no longer caring about the "power
user" - the sort of person who can cope with VBA, but does not have
the time to move to C# etc - the sort of person who cares a lot about
Microsoft's products, uses all of their advanced features, and does
not need Ribbons etc.

Does any one else have any views on this?

Julian

 

[Doug Robbins - Word MVP]

We do know that VBA will be retained in at least the next version of Word.

However, once you get the hang of it, Customizing the Ribbon is not really
difficult.

See the article "Customize the Ribbon (It doesn't take Rocket Science) on
fellow MVP Greg Maxey's website at:

http://gregmaxey.mvps.org/Customize_Ribbon.htm

I guess that you also have to ask yourself Do I really need to switch (I
nearly said "upgrade", but that might be the wrong word) to the latest
version if it does not add something that I really need.

--
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, originally posted via msnews.microsoft.com

 

[Cindy M.]

Hi Julian,

Supplementing Doug's reply (with which I fully agree)...

In an ideal world, especially, I would like to be able to create,
using VBA, a dockable custom TaskPane to hold all my VB routines
(rather than a modeless UserForm or custom tool bar in the Add-In
Ribbon), but I note that to be able to do this, it seems I need to
master COM based Add-Ins and aquire C# / VB.NET skills as well as a
professional version of Visual Studio.

I believe it's possible to program a COM add-in with the old VB6 to
use a CTP. It's not something I've ever done, but I think a couple of
the Excel and Outlook MVPs have successfully done so.

As to using .NET: I understand that the tool Addin Express (www.add-
in-express.com) can make some of these daunting tasks much easier. I
have no experience with it, but the developer team drops into the
office.developer.com.add_ins newsgroup regularly. They may also have
information on their site that would give you an idea how big the
learning curve is and how expensive that would be (compared to, say
VS .NET Pro).

It's also possible to program a "COM add-in" using VB.NET Express
(the free version), but that learning curve could be rather steep.

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

 

[Julian Turner]

We do know that VBA will be retained in at least the next version of Word..

However, once you get the hang of it, Customizing the Ribbon is not really
difficult.

See the article "Customize the Ribbon (It doesn't take Rocket Science) on
fellow MVP Greg Maxey's website at:

http://gregmaxey.mvps.org/Customize_Ribbon.htm

I guess that you also have to ask yourself Do I really need to switch (I
nearly said "upgrade", but that might be the wrong word) to the latest
version if it does not add something that I really need.

--
Hope this helps.

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

Dear Doug

Thank you for your reply. I take a lot of comfort that VBA will
remain for at least the next version, as I have (as I am sure many
have) developed a lot of code in it - although at the same time I do
appreciate that Microsoft has its reasons for wanting to drive change,
and I know that .NET is the future.

The main advantage of VBA is that I can hack together lots of tools
for myself without needing to consult with my IT department or fight
with any security software on my work PC.

VB macros give me the perfect way to develop useful productivity
enhancements for Word, for which I am most thankful to Microsoft. In
particular I use VB to provide enhanced versions of existing Word
tasks, such as an enhanced cross-reference system, that enables me to
switch in and out of the document for minor edits without having to
refresh the paragraph list each time (something that the built-in
cross-reference dialogue requires).

I do like the Ribbon in general. My main niggle with the Ribbon was
that if I am using several commands at the same time and they are on
different ribbons, it means more clicking, whereas in Word 2003 I can
nestle the commands close to each other.

The article on customising the Ribbon looks very useful, and I think I
do need to grasp the nettle, and learn more. I have a pretty good
amateur knowledge of programming, and have studied some of .NET, so I
know that it is not beyond me.

In terms of whether to upgrade, you make a good point. I squeeze as
much out of Word 2003 as I can, and Word 2007 does not give me much
more I need in terms of functionality, but I do appreciate a lot of
its user interface improvements. I

have Office 2007 at home and Office 2003 at work, so I am currently
caught between both worlds! Hence I have now moved all my macros into
a Multi-Tab control in a UserForm (rather than in a CommandBar) so
that they are easily transferrable between the two systems.

Time to start preparing for the future I guess.

Regards

Julian

 

[Julian Turner]

Hi Julian,

Supplementing Doug's reply (with which I fully agree)...


I believe it's possible to program a COM add-in with the old VB6 to
use a CTP. It's not something I've ever done, but I think a couple of
the Excel and Outlook MVPs have successfully done so.

As to using .NET: I understand that the tool Addin Express (www.add-
in-express.com) can make some of these daunting tasks much easier. I
have no experience with it, but the developer team drops into the
office.developer.com.add_ins newsgroup regularly. They may also have
information on their site that would give you an idea how big the
learning curve is and how expensive that would be (compared to, say
VS .NET Pro).

It's also possible to program a "COM add-in" using VB.NET Express
(the free version), but that learning curve could be rather steep.

Cindy Meister
INTER-Solutions, Switzerlandhttp://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

Hi Cindy

Thank you too for your reply.

I did notice the ICTPFactory Object in the help documentation (with C#
references) so perhaps I might have a go at this, and see if I can
find some of the solutions you mentioned.

Add-in express looks powerful, but outside my budget out the moment.

I have got VB Express installed, so I might actually have a go at
programming a COM add in, and tackling that learning curve. I have
been looking a little at .NET (I understand that VB.NET is a different
beast to VB6), and have a vague appreciation of what I might be up
against.

Thanks again.

Regards

Julian

 

[Doug Robbins - Word MVP]

Hi Julian,

When Microsoft dumps VBA and nobody uses it anymore, I will go the way of
the dinosaurs.

--
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, originally posted via msnews.microsoft.com

We do know that VBA will be retained in at least the next version of Word.

However, once you get the hang of it, Customizing the Ribbon is not really
difficult.

See the article "Customize the Ribbon (It doesn't take Rocket Science) on
fellow MVP Greg Maxey's website at:

http://gregmaxey.mvps.org/Customize_Ribbon.htm

I guess that you also have to ask yourself Do I really need to switch (I
nearly said "upgrade", but that might be the wrong word) to the latest
version if it does not add something that I really need.

--
Hope this helps.

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

Dear Doug

Thank you for your reply. I take a lot of comfort that VBA will
remain for at least the next version, as I have (as I am sure many
have) developed a lot of code in it - although at the same time I do
appreciate that Microsoft has its reasons for wanting to drive change,
and I know that .NET is the future.

The main advantage of VBA is that I can hack together lots of tools
for myself without needing to consult with my IT department or fight
with any security software on my work PC.

VB macros give me the perfect way to develop useful productivity
enhancements for Word, for which I am most thankful to Microsoft. In
particular I use VB to provide enhanced versions of existing Word
tasks, such as an enhanced cross-reference system, that enables me to
switch in and out of the document for minor edits without having to
refresh the paragraph list each time (something that the built-in
cross-reference dialogue requires).

I do like the Ribbon in general. My main niggle with the Ribbon was
that if I am using several commands at the same time and they are on
different ribbons, it means more clicking, whereas in Word 2003 I can
nestle the commands close to each other.

The article on customising the Ribbon looks very useful, and I think I
do need to grasp the nettle, and learn more. I have a pretty good
amateur knowledge of programming, and have studied some of .NET, so I
know that it is not beyond me.

In terms of whether to upgrade, you make a good point. I squeeze as
much out of Word 2003 as I can, and Word 2007 does not give me much
more I need in terms of functionality, but I do appreciate a lot of
its user interface improvements. I

have Office 2007 at home and Office 2003 at work, so I am currently
caught between both worlds! Hence I have now moved all my macros into
a Multi-Tab control in a UserForm (rather than in a CommandBar) so
that they are easily transferrable between the two systems.

Time to start preparing for the future I guess.

Regards

Julian

 

[Julian Turner]

Hi Julian,

When Microsoft dumps VBA and nobody uses it anymore, I will go the way of
the dinosaurs.

--
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, originally posted via msnews.microsoft.com"Julian Turner" <[email protected]> wrote in message

Hi Doug

It will be a sad day for the intelligent but non-professional-
programmer if Microsoft does make that decision.

I have no grudge in upgrading Word when a new version comes out, and I
do every time; but I will resist if it cuts me off from what makes
Word fun and useful - rapid macro development.

Visual Basic + Word gives me a quick and easy way into productivity.
I can go from development to test to deploy in minutes, to a couple of
hours.

It also lets me be more ambitious. I have created in one day
templating systems where one document acts as a "form" which I fill
in, and the Macros then load up template contracts, fill in book-
marked boxes and tables, and effectively general complex consumer
credit documentation,

I have now had a look at Add-In programming for Office, and aside from
the cost of getting a professional version visual studio (express does
not contain any useful templates it seems), the level of skill
required to create and hook up an Add-In, puts it outside my realistic
range of options for the moment. I could probably do it, but as
Cindy said, the learning curve is steep.

I would like to end with a plea to Microsoft - don't forget the power
user - and keep programming fun!

Regards

Julian