I’ve been thinking a lot lately about when I will stop writing code that works in Excel 97 (like the Split function, for example). I’m interested in to see what other people are doing.
| When will you stop writing Excel97 compliant code? | |
| I already have. | |
| After the next version. | |
| When I/my company upgrade(s) from 97. | |
| When nobody on the planet uses it. | |
| When nobody I know uses it. | |
| I don’t understand the question. | |
| These choices stink. See my comment. | |
|
|
|
| Free polls from Pollhost.com | |
With Excel 2003 out I now have to test all my VBA applications in four versions of Excel. It’s such a pain but I do have customers with these different versions. I have found many undocumented differences between the same code in these four versions. I never use references (so I don’t have to deal with installing a .dll on the customer’s PC) and always use what’s only available in xl97 but there are still many times when the code won’t work in newer versions. There are also times when it works in newer versions but not older. I don’t want to write code for each version of Excel so this greatly increases the amount of time it takes to release a new application. When Microsoft says Excel is backward compatible they’re NOT talking about VBA.
“code won’t work in newer versions” ? I haven’t encountered that -and it shouldn’t happen in theory. Could you post a sample ?
The secret of health for both mind and body is not to mourn for the past, worry about the future, or anticipate troubles but to live in the present moment wisely and earnestly. Tramadol onlineThe secret of health for both mind and body is not to mourn for the past, worry about the future, or anticipate troubles but to live in the present moment wisely and earnestly. Tramadol online
sorry this is an “out of the way” test
for next
sub