"DWilliams" wrote in message
...
On another variant, is there a POINT to becoming a "VBA guru" anymore?
Will
"Visual Studio for Applications" completely replace VBA like VB.NET did
VB6?

http://vsip.summsoft.com/vsa/docs/cu...MandDOTNET.asp


Undoubtedly but .net is similar enough to VB/VBA to make it
a reasonable progression and they have made C# much more accessible
than C or C++ ever were.

Keith

"Mark Lewis" wrote in message
...
I have not looked at Visual Studio for Applications yet but vb.net is
really
a totally different language than vb6. If it is as hard to migrate code
from
VBA to the new product, as I expect, then the transition will be a slow
process and require significant knowledge of both languages to pull it
off.
Not sure if this will be harder than the switch to VBA from the old macro
language or not. The basic worksheet/cell structure will remain.


It looks daunting at first but once you get into it its really
not so bad. The real problems will arise if you have lots of
undeclared variables since these default to variants in VBA
and VB.net has no such thing

Keith

Thanks. That is good news.

In vb.net you can use Objects to sub for Variants if you like. I prefer, as
I suspect you do from your comment, to just go ahead and define them
properly.

Mark



"Keith Willshaw" wrote in message
...

"Mark Lewis" wrote in message
...
I have not looked at Visual Studio for Applications yet but vb.net is
really
a totally different language than vb6. If it is as hard to migrate code
from
VBA to the new product, as I expect, then the transition will be a slow
process and require significant knowledge of both languages to pull it
off.
Not sure if this will be harder than the switch to VBA from the old
macro
language or not. The basic worksheet/cell structure will remain.


It looks daunting at first but once you get into it its really
not so bad. The real problems will arise if you have lots of
undeclared variables since these default to variants in VBA
and VB.net has no such thing

Keith