97 code vs. 2000 and 2002
 

Hi All..........
Is there any kind of program or code that can be run to check code that was
written in XL97 and see if it is compatible with XL2000 and/or XL2002? I
have a program written in 97, several years ago and has worked fine ever
since, till lately when some users have upgraded and saved the program in
their respective versions. Some of the macros are acting flaky.

Any thoughts would be appreciated....

Vaya con Dios,
Chuck, CABGx3

97 code vs. 2000 and 2002
 

Nothing I am aware of.

I think you would have to look at objects that behave differently in the
later version.

for instance

in excel 97

set rng = Range("A1,A5,A7,A11").EntireRow

would be a reference to Row(1). In xl2000 and later it would be what you
hoped

set rng = Range("A1,A5,A7,A11").EntireRow
? rng.Address
$1:$1,$5:$5,$7:$7,$11:$11

I can't say what those are off the top of my head, but it isn't many.
Perhaps a review of what objects you are working with.

--
Regards,
Tom Ogilvy



"CLR" wrote:

Hi All..........
Is there any kind of program or code that can be run to check code that was
written in XL97 and see if it is compatible with XL2000 and/or XL2002? I
have a program written in 97, several years ago and has worked fine ever
since, till lately when some users have upgraded and saved the program in
their respective versions. Some of the macros are acting flaky.

Any thoughts would be appreciated....

Vaya con Dios,
Chuck, CABGx3

97 code vs. 2000 and 2002
 

Thanks Tom..........I guess it was just wishful thinking.........

Vaya con Dios,
Chuck, CABGx3



"Tom Ogilvy" wrote:

Nothing I am aware of.

I think you would have to look at objects that behave differently in the
later version.

for instance

in excel 97

set rng = Range("A1,A5,A7,A11").EntireRow

would be a reference to Row(1). In xl2000 and later it would be what you
hoped

set rng = Range("A1,A5,A7,A11").EntireRow
? rng.Address
$1:$1,$5:$5,$7:$7,$11:$11

I can't say what those are off the top of my head, but it isn't many.
Perhaps a review of what objects you are working with.

--
Regards,
Tom Ogilvy



"CLR" wrote:

Hi All..........
Is there any kind of program or code that can be run to check code that was
written in XL97 and see if it is compatible with XL2000 and/or XL2002? I
have a program written in 97, several years ago and has worked fine ever
since, till lately when some users have upgraded and saved the program in
their respective versions. Some of the macros are acting flaky.

Any thoughts would be appreciated....

Vaya con Dios,
Chuck, CABGx3

97 code vs. 2000 and 2002
 

The only change that I am aware of where the code is drasticaly different is
in pivot tables. In 2002 MS implimented a new pivot table engine and as a
result the code is a bit different. If you have pivot table code then you
need to rework it. Otherwise there are a few changes as Tom mentions.
--
HTH...

Jim Thomlinson


"CLR" wrote:

Hi All..........
Is there any kind of program or code that can be run to check code that was
written in XL97 and see if it is compatible with XL2000 and/or XL2002? I
have a program written in 97, several years ago and has worked fine ever
since, till lately when some users have upgraded and saved the program in
their respective versions. Some of the macros are acting flaky.

Any thoughts would be appreciated....

Vaya con Dios,
Chuck, CABGx3

97 code vs. 2000 and 2002
 

Thanks for the info Jim.........

Vaya con Dios,
Chuck, CABGx3



"Jim Thomlinson" wrote:

The only change that I am aware of where the code is drasticaly different is
in pivot tables. In 2002 MS implimented a new pivot table engine and as a
result the code is a bit different. If you have pivot table code then you
need to rework it. Otherwise there are a few changes as Tom mentions.
--
HTH...

Jim Thomlinson


"CLR" wrote:

Hi All..........
Is there any kind of program or code that can be run to check code that was
written in XL97 and see if it is compatible with XL2000 and/or XL2002? I
have a program written in 97, several years ago and has worked fine ever
since, till lately when some users have upgraded and saved the program in
their respective versions. Some of the macros are acting flaky.

Any thoughts would be appreciated....

Vaya con Dios,
Chuck, CABGx3