Excel VBA Backwards Compatability Problem - 2002->97

  • Thread starter Thread starter reniep
  • Start date Start date
R

reniep

I have a created an Excel workbook with some fairly complicated VBA
scripts in Office2002. The workbook is apparently being sent to some
folks in Guadalajara who are using Office97. These folks are having
problems running the scripts, so I suspect it's due to VBA that
Office97 doesn't recognize. I don't know the specific error as of
right now.

My question is: short of installing Excel97 or otherwise taking over
someone's PC, is there a conversion utility that will identify
incompatible code between the two versions, or another automated
solution I can try to troubleshoot this?

Here is what I've tried thus far:
(1) I went through the 8 page list of "new" VBA objects that Microsoft
put out for Office2000, but that proved of no help.
(2) Saved the workbook in 97/2000 & 95 format with no errors. Sent that
to the folks on Office97..they stlil get the same error.

Any suggestions or hints would be greatly appreciated. I'm pretty sure
I'm not using any new functions or syntax, since everything I wrote was
based off of my knowledge from the 97 version!

Thanks,
Irene
 
Irene;

VBA / Macro language in Office 2002 differs a lot from 97 in some fields.
I can't list them all, but it might well be that the code you wrote is not
supported by the office 97 version and therefore will never work on your
friend's system.

Mark.

More Excel ? www.rosenkrantz.nl or (e-mail address removed)
 
If you recorded any of the code, then many objects have additional arguments
that while optional, when you recorded the code, it places them in the
recorded code. Excel 97 will error on those statements because it does not
recognize the argument.

Also, useful functions such as instrRev, split, join, replace were
introduced in VBA6 (xl2000) while Excel 97 used VBA5. This is in addition
to any new objects.

There is not utility that I am aware of that will identify these type
problems, beyond getting Excel 97 and compiling the code, then fix the
errors as they occur.
 
Andy Wiggins said:
I think that installing Excel 97 is your best option.
Click to expand...
....

Indeed! Another case proving the wisdom of giving developers the *oldest*
versions of software that would be used by anyone in their organization,
ideally also the slowest machines that would be used by anyone else.
 
Back
Top