Binding is only an issue with automation. It doesn't sound like you're
using automation but if you are tell us what app you're automating Excel
from.

Pick out a snippet of code that you find fails in Excel 2003 but runs in
2000. Copy it into its only little sub in a new workbook and run that sub
in both versions. If you find that it still fails in 2003 and runs in 2000
post it here so we can figure out why. If it does run you have to figure
out what is different in the problem workbook. We can help maybe but it's
hard without the workbook/code.

--
Jim Rech
Excel MVP
"Wboson" wrote in message
...
Already read many posts on object models, early & late binding. One
suggestion put forth for overcoming the incompatibilities of object models
is
to program in an earlier version; it should port forward. This has not
been
my (limited) experience. I had to build a macro/VBA combination that
worked
in Excel 2002 to overcome errors from opening and running the macros/VBA
built in Excel 2000. Once this was done it is now not backward compatible.

I have tried inspecting the Excel version number and executing different
code but this also fails. The commands that fail are setting border
thickness, colors, cell shading and cell protection. Can you point out
additional resources on 'binding'; is this required with an Excel
macro/VBA
solution? (It is not a compiled app.)

There are many hidden sheets and locked cells in my solution. Excel
auto-prompts for the password when an error occurs. Is there a better
method
of pgm to avoid the auto password request?

Is there a resource on commands/parameters available in differing versions
of Excel?

Thank You for your time.
--
John