Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I do volunteer work with an out-of-state non-profit organization that runs
Office 2000. I wrote several VBA programs for them using Excel 2002. I sometimes get nailed on revisions that I send because of my newer version. Almost always the problem is that I included system defined variables (usually generated when I record a macro) that were not used in the prior version. Can anyone offer an easy way for me to check the code for back compatabiity before I send it to them. Thanks for any suggestions. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
97 code vs. 2000 and 2002 | Excel Programming | |||
Excel 2000 to 2002 - #NAME? | Excel Discussion (Misc queries) | |||
XL 2002 vba on an XL 2000 machine | Excel Programming | |||
Excel 2000 and 2002 | Excel Programming | |||
2000 vs 2002 xConstants | Excel Programming |