One of the big sticky points of switching between versions of the same
application, certain codes are modified, so to get around such issues, you
often times end up having to use late binding rather than early binding. To
use late binding, it's very tedious as you can't use some of the features
that you can with early binding. A lot of that has to do with the fact that
when using late binding, compilation of the code takes place at "Run-Time"
rather than at "Design-Time", as what happens with early binding. While
late binding gives you the advantage of being version independent, it also
runs a lot slower than early binding. To read up more on the difference
between early binding and late binding as well as how to late bind code,
look at the following links:

http://word.mvps.org/FAQs/InterDev/E...ateBinding.htm

http://peltiertech.com/Excel/EarlyLateBinding.html

"Jim Hunt" wrote in message
...
I have created a spreadsheet application that I need to distribute. I
originally wrote it using Excel 2007. I then moved it to 2003. Even when
running 2003 on my machine, it is using VBA 6.5. Is there a way to a)
force
it to use an older version or b) an easy way (other than upgrading to
Office
2007) for an Office 2003 user to load VBA 6.5?

Thanks.