If you need to have you code running on multiple Excel versions, then you
have two choices:

1. Code with the earliest version you wish to support. and use early
binding. Restrict the statements used to only those that will work in the
earliest version you wish to support. Note that you may still encounter code
that does not work the same, if at all, in more recent versions of Excel.

2. Code with the latest version you wish to support and use late binding,
Restrict the statements used to only those that will work in the earliest
version you wish to support, Note that you may still encounter code that
does not work the same in earlier versions of Excel, especially with Excel
97.

There is actually a 3rd choice, but it is more difficult. One can construct
code so that some parts use version dependent code, but this gets tricky.

The overall task can oft be made easier if one codes in VB 6 (automating
Excel via VB 6), instead of Excel, because the VB 6 code would allow you to
use certain code that would not otherwise work in Excel 97, not to mention,
the code should execute faster and would be protected from prying eyes.

--
http://www.standards.com/; See Howard Kaikow's web site.
"Joe Blow" wrote in message
news:DOvuc.593189$Pk3.417214@pd7tw1no...
Visual Studio ? I believe the languages are identical, with no new or
changed methods or properties.

So the problems I am having are due to the Excel macro being run on a
different machine, not becuase the other machine doesn't have the .3?

But you should take this to a Visual Basic newsgroup, this place deal
with
Excel.

Well, it is an Excel macro that I programmed that I am having the problem
with.



HTH. Best wishes Harald


"Joe Blow" skrev i melding
news:78duc.586228$Pk3.216793@pd7tw1no...
I wrote a written a very nice utility in 6.3 for work. Of course I
find
out
that work has 6.0 and it doesn't like some of the things in my macros.
Do
I
re-write the code at work? Can I make 6.3 think that it is 6.0? This
has
to
be a common enough thing. Any help appreciated.