Hi to all,
I have a dilemma and I hope there is some simple solution.
I often create macros in Excel ... nothing too deep, just some aides for data entry, error trapping, and reporting. I know little about VBA, but I have been able to go in now and then and make some changes and corrections successfully.
Many months ago, I changed to Office 2007, and after a little "getting used to it", I love it. But, because many still use Office 2003, I have to save my documents in 2003 format. I noticed immediately that there are some formatting differences, and Excel is quick to warn me of that when I 'save as', but aside from some color and formatting issues, I haven't had too many problems ... up til now.
I recently completed yet another macro-writing exercise, got it all de-bugged, and it works great. I can 'save as' and get the typical 'format' warnings, but what I find now (this is the first time I created some 'code' to hand to another using Excel 2003), it just won't work properly. It's not an issue of 'macro security' or the like, but down to the VBA itself, not recognizing some syntax. Now I'm stuck.
I've got two machines, but both have Excel 2007, so I can't 'proof' anything before I hand it out. I have no machine with Excel 2003, so I can't create the original macros there. (I have learned that there is forward compatibility, as older work I did before in 2003 works find in 2007).
What I'm hoping for is some way to solve this within the 2007 platform I have. Can it emulate 2003? Is there a way to 'test' 2007 VBA code for compatibility with 2003? Is there a way to 'convert' 2007 VBA code to 2003?
Folks, I'm open to all comments and suggestions.
Thanks in advance, and kind regards ...
Excel 2007 vs. Excel 2003
Re: Excel 2007 vs Excel 2003
"Almost" Good Answers: