I wrote a macro in Excel 2000. Part of it checks a
particular cell and reads the value. This cell should be
a number (and is defined as such). When a client trys to
use my macro on Excel 97 he gets a run time error, type
mismatch. When he opens visual basic it points to the
line where I check the value of this cell to see if it
already appear in a database keep in a separate sheet. I
am not able to recreate this on my computer. Also I am
using protected and unprotected cell on is sheet too (I am
not sure if this would be related). The run-time error
appears when he tries to execute my macro. Do you have
any advice?

Andy,

If you develop for 3rd parties..

If you dont have an old copy of Excel97 lying around, then you'll have a
problem... else I'd advise you to install excel97. (different versions can
be installed on the same machine without problems, but it is advisable to
install them in "ascending" sequence starting with the olders version.)

You may do your development in your more recent version,
but CAN test for compatibility in Excel97 when required.

You cant begin to guess the number of changes nor their little
intricacies. You'll need to debug yourself on xl97.

After a while you'll get a feeling of what to avoid when building for
older versions... Or simply decide to develop in xl97 in the first place.

Excel 2000 has a whole bunch of enhancements. Protection structure among
them. VBA version increased to VBA6 and includes many little things that
you have have used unknowingly. (split, instrrev ?)

Check MSDN or VBA help and start with "What's new"
Alas I dont know a site that has a comprehensive list of ALL the changes..

If you want.. and if it's not 10 modules and 2000 lines of code...
email your book to me (ZIPPED!)...and I'll have a look.
address below.



keepITcool

< email : keepitcool chello nl (with @ and .)
< homepage: http://members.chello.nl/keepitcool


"Andy" wrote:

I wrote a macro in Excel 2000. Part of it checks a
particular cell and reads the value. This cell should be
a number (and is defined as such). When a client trys to
use my macro on Excel 97 he gets a run time error, type
mismatch. When he opens visual basic it points to the
line where I check the value of this cell to see if it
already appear in a database keep in a separate sheet. I
am not able to recreate this on my computer. Also I am
using protected and unprotected cell on is sheet too (I am
not sure if this would be related). The run-time error
appears when he tries to execute my macro. Do you have
any advice?