Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Excel 2000 v 2003 Macro & VBA Incompatibility
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 |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Windows Vista and Excel 2000 -- incompatibility? | Excel Discussion (Misc queries) | |||
Office 2000 Excel Macro runs very slow in 2003, why? | Excel Discussion (Misc queries) | |||
Macro error after switching from Excel 2000 to Excel 2003 | Excel Discussion (Misc queries) | |||
Excel 2000 v 2003 Macro & VBA Incompatibities | Excel Programming | |||
Macro written in Excel 2003 and saved as Excel 2000 .xls | Excel Programming |