I should clarify that my statement

"..., and so far we've identified more issues than we've been able to work
around."

doesn't mean that the issues are insurmountable. Given time and resources we
will figure out how to make them work. But many are simple inconsistencies,
and others are features which were not yet available in the beta.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"RonF" wrote in message
...
A very big "thanks" to JLatham, Jim Rech, Gary Keramidas, and Jon Peltier
for
the replies and advice.

Quoting from Jon's reply "..., and so far we've identified more issues
than
we've been able to work around." ... this is just the type of concern that
we
thought might exist.

Again, many thanks to all those responded and hopefully this has been
helpful to others as well.

Ron

"RonF" wrote:

First let me say that I am a total novice as far as VBA is concerned and
how
it runs under various versions of Excel.

My company has a "commercial" data application that is an Excel
spreadsheet
with underlying VBA code that is very, very complicated.

We are now trying to determine what, if any, issues do we face with
upcoming
releases of Vista and Office 2007. In other words, if the VBA is written
with our Excel 2002 and sent to clients, will there be any issues if
clients
are using newer operating systems or newer versions of Excel? So far,
things
seem to work just fine, but we're not sure what might be looming out
there
that we don't see.

Lastly, given Microsoft's emphasis on the .NET languages, is VBA on the
"short list" for being no longer supported assuming that VBA programmers
will
be migrating to VB.net applications and using it instead?

Again, I aplogize for not being fluent or knowledgeable on VBA but the
articles that I have found on Google and Microsoft don't seem to answer
the
questions. Could be that I was searching on the right key words.

Therefore, any help would be very much appreciated.

Thanks,

Ron