Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi. I am writing macros in 2002 and would like for people using 2000 to be
able to us the macros. I am running into problems ... Is there a compatability issue between the two? Is there a way around this other than having the others upgrade? Thanks, Mike. |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
What sort of problem?
-- _______________________ Naz, London "Mike D." wrote: Hi. I am writing macros in 2002 and would like for people using 2000 to be able to us the macros. I am running into problems ... Is there a compatability issue between the two? Is there a way around this other than having the others upgrade? Thanks, Mike. |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Mike,
The best way to do this is to write your code in 2000 and get it working then test it in 2002. It is more likely to be compatible that way around. Robin Hammond www.enhanceddatasystems.com "Mike D." wrote in message ... Hi. I am writing macros in 2002 and would like for people using 2000 to be able to us the macros. I am running into problems ... Is there a compatability issue between the two? Is there a way around this other than having the others upgrade? Thanks, Mike. |
#4
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi Mike
I run into to similar problems with developing in XL 2002 and XL 97, the problems seem to lie in two areas..... 1. Commands that either are non-existent or have extended features. 2. Sublte changes in the way VBA deals with variables formats etc. The first is the easiest to spot but most difficult to fix, usually VBA throws an error and you then need to explore differences, unfortunately the fix often means a code section rewrite. The second is simplest to fix but the most annoying as it is not always obvious what the problem is. Recently I had a procedure that worked fine in XL2002 - it tested for a numerical value on a worksheet, in XL97 the same worksheet thru an errror - type mismatch. The worksheet value was in fact a string (numerical characters!). The fix in XL97 worked fine in XL2002. I guess the best approach (if possible) is to work in the oldest version and test in the later version(s). Froward compatability is more likely - but not always guaranteed! -- Cheers Nigel "Mike D." wrote in message ... Hi. I am writing macros in 2002 and would like for people using 2000 to be able to us the macros. I am running into problems ... Is there a compatability issue between the two? Is there a way around this other than having the others upgrade? Thanks, Mike. |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
How do you set Excel 2002 as the default program? | Setting up and Configuration of Excel | |||
Excel 2002 - Program breakdown while saving | Excel Discussion (Misc queries) | |||
Range.calculate debug, Excel 2000 VBA compatability with Excel XP | Excel Programming | |||
Excel VBA Backwards Compatability Problem - 2002-97 | Excel Programming | |||
Excel 2002 and 97 compatability | Excel Programming |