I do volunteer work with an out-of-state non-profit organization that runs
Office 2000. I wrote several VBA programs for them using Excel 2002. I
sometimes get nailed on revisions that I send because of my newer version.
Almost always the problem is that I included system defined variables
(usually generated when I record a macro) that were not used in the prior
version.

Can anyone offer an easy way for me to check the code for back compatabiity
before I send it to them.

Thanks for any suggestions.

The only safe way is to actually write it in 2000. That being said there are
a few main compatabilty culprets. Pivot tables changed drastically in 2002 (a
whole new data engine). Nothing about pivot table code is portable between
the 2 versions. Some references are updated in 2002 (specifically Microsoft
ActiveX Data Objects 2.8).

The biggest one however is sort routines include and extra parameter.
(DataOption1:=xlSortNormal) Which can just be deleted as xlSortNormal is the
default. If the prameter is anything else then you need to worry about
compatiability as you are using a feture that does not exist in 2000...
--
HTH...

Jim Thomlinson


"Bonsai Bill" wrote:

I do volunteer work with an out-of-state non-profit organization that runs
Office 2000. I wrote several VBA programs for them using Excel 2002. I
sometimes get nailed on revisions that I send because of my newer version.
Almost always the problem is that I included system defined variables
(usually generated when I record a macro) that were not used in the prior
version.

Can anyone offer an easy way for me to check the code for back compatabiity
before I send it to them.

Thanks for any suggestions.

Hi Jim,

Thanks for your reponse, although it was not the answer I was hoping for.
Fortunately I was not using pivot tables but will remember that.

The sort variable you mentioned got me. Here are some more that that I
remember:

PrintQuality
PrintErrors
Tab.Color

I will probably move on to Office2007 later this year so I expect there will
be more goctha's when I do.

"Jim Thomlinson" wrote:

The only safe way is to actually write it in 2000. That being said there are
a few main compatabilty culprets. Pivot tables changed drastically in 2002 (a
whole new data engine). Nothing about pivot table code is portable between
the 2 versions. Some references are updated in 2002 (specifically Microsoft
ActiveX Data Objects 2.8).

The biggest one however is sort routines include and extra parameter.
(DataOption1:=xlSortNormal) Which can just be deleted as xlSortNormal is the
default. If the prameter is anything else then you need to worry about
compatiability as you are using a feture that does not exist in 2000...
--
HTH...

Jim Thomlinson


"Bonsai Bill" wrote:

I do volunteer work with an out-of-state non-profit organization that runs
Office 2000. I wrote several VBA programs for them using Excel 2002. I
sometimes get nailed on revisions that I send because of my newer version.
Almost always the problem is that I included system defined variables
(usually generated when I record a macro) that were not used in the prior
version.

Can anyone offer an easy way for me to check the code for back compatabiity
before I send it to them.

Thanks for any suggestions.