What Is the Future of Excel VBA ?

[Ken1000]

Hi. I'm using Excel 2003.

With Excel 12 and the new Windows system Vista ahead, what is the
future of Excel VBA coding ? Will previous coding procedures still
work in these products ? Will there be a new set of commands to
learn ? Or, a new language to learn other than VBA ?

Also, will certain Excel versions, such as 2000, no longer be supported ?

I'd appreciate any information on this.

Thank you.

Ken

 

[gwkenny]

huh?

Huh?

Why ask about something that hasn't arrived?

I don't think anyone can tell you much.

But the fact remains that backward compatibility is one of the main assets to retain one's software client base I don't think they can go change things wholesale.

What I DO hope is that Microsoft really unifies the VB between Microsoft apps.

Coding in PowerPoint to Word to Excel is the definition of being pschitzophrenic (or whoever you spell that). Add Access to the mix and you become psychotic.

Toss in Outlook as well and you have the makings of an insane individual.

 

[davisaggie]

Ken1000 wrote:

Hi. I'm using Excel 2003.

With Excel 12 and the new Windows system Vista ahead, what is the
future of Excel VBA coding ? Will previous coding procedures still
work in these products ? Will there be a new set of commands to
learn ? Or, a new language to learn other than VBA ?

Also, will certain Excel versions, such as 2000, no longer be supported ?

I'd appreciate any information on this.

Thank you.

Ken

I have the same questions as Ken does. Now that XL 12 is closer to release does anyone know more about VBA support in Vista? I've heard rumors that VBA support is going away, is that true? If so what is replacing it?

Thanks,
Mike

 

[Smitty]

Check out Microsoft's Visual Studio Tools for Office Portal.

HTH,

Smitty

 

[SydneyGeek]

From the stuff I've read, VBA will be replaced down the track. Office 2007 will support VBA code for compatibility reasons but MS is moving to using the .NET Framework for code.

But, given that Excel 2007 VBA Programmer's Reference is shipping in March next year (along with several other Excel 2007 VBA books), you won't have to jump ship yet.

However, there will be tighter security -- now, unsigned macros run if you elect to enable them. In 2007, they will be disabled *unless* they are signed.

And, if your code creates custom menus, you will need to change that code because the Ribbon is replacing menus as we know them.

See ... http://www.directionsonmicrosoft.com/sample/DOMIS/update/2006/06jun/0606ccmto2.htm
...and, for customising the Ribbon,
http://www.xtremevbtalk.com/showthread.php?s=c122b7e8d058a7ea7d6223dc784f4fbd&p=1163030#post1163030

Denis

 

[Joe C]

We have SAP at work and it uses BW, which basically in part uses VBA programing. How in the World is BW going to adjust systems to work in 2 enviroments of Excel?

 

[SydneyGeek]

We have SAP at work and it uses BW, which basically in part uses VBA programing. How in the World is BW going to adjust systems to work in 2 environments of Excel?

From what I've seen, you should stick to the lowest version you need to support. That way, you don't have issues with new bits of the object model -- but watch out for VBA that manipulates charts, because they have been extensively updated.
Then, sign the code in the workbooks. It won't affect earlier users but it will make the 2007 workbooks usable

Denis