Excel 2000 v 2003 Macro & VBA Incompatibities
 

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 locked/protected cells
and sheets; when an error ocurrs Excel prompts for the password. Can you
suggest a better work-around then to have Excel auto-prompt for the password.
(Everyone wants to unlock and unhide data to get around the errors.)

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

Thank You for your time.
--
John

Excel 2000 v 2003 Macro & VBA Incompatibities
 

Backward compatibility cannot be guaranteed, forward is more
straight-forward.

--

HTH

RP
(remove nothere from the email address if mailing direct)


"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 locked/protected
cells
and sheets; when an error ocurrs Excel prompts for the password. Can you
suggest a better work-around then to have Excel auto-prompt for the
password.
(Everyone wants to unlock and unhide data to get around the errors.)

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

Thank You for your time.
--
John