![]() |
VB code needed for running newer excel version macros in older excel versions
Hi all,
When trying to run a macro, created in excel XP, on a pc with excel 2000 installed, the macro will find codes that are not recognized in the older excel versions and therefore not finish running. Is there any (simple) coding available to avoid these problems from happening? Thanks, Tom |
VB code needed for running newer excel version macros in older excel versions
is there another way then creating the macro in the older
excel version? this takes tooo long (e.g. siable the feature in excel 2000? -----Original Message----- You need to eliminate the use of features of Excel 2002 VBA not supported by Excel 2000 VBA. One way to do this is to develop the code using Excel 2000, instead of Excel 2002. -- http://www.standards.com/; See Howard Kaikow's web site. "Tom" wrote in message ... Hi all, When trying to run a macro, created in excel XP, on a pc with excel 2000 installed, the macro will find codes that are not recognized in the older excel versions and therefore not finish running. Is there any (simple) coding available to avoid these problems from happening? Thanks, Tom . |
VB code needed for running newer excel version macros in older excel versions
You need to eliminate the use of features of Excel 2002 VBA not supported by
Excel 2000 VBA. One way to do this is to develop the code using Excel 2000, instead of Excel 2002. -- http://www.standards.com/; See Howard Kaikow's web site. "Tom" wrote in message ... Hi all, When trying to run a macro, created in excel XP, on a pc with excel 2000 installed, the macro will find codes that are not recognized in the older excel versions and therefore not finish running. Is there any (simple) coding available to avoid these problems from happening? Thanks, Tom |
VB code needed for running newer excel version macros in older excel versions
"tom" wrote in message ... is there another way then creating the macro in the older excel version? this takes tooo long (e.g. siable the feature in excel 2000? Just do a save as into Excel 2000 format and open Excel 2000 , you should get the errors when you compile It that doesnt work export the code modules from 2002 and load em into 2000 Keith |
VB code needed for running newer excel version macros in older excel versions
there is no difference in formats since xl97.
Getting the compile errors is what he is getting now. He wants some automatic way to fix them - I don't believe there is a way to do that. -- Regards, Tom Ogilvy "Keith Willshaw" wrote in message ... "tom" wrote in message ... is there another way then creating the macro in the older excel version? this takes tooo long (e.g. siable the feature in excel 2000? Just do a save as into Excel 2000 format and open Excel 2000 , you should get the errors when you compile It that doesnt work export the code modules from 2002 and load em into 2000 Keith |
VB code needed for running newer excel version macros in older excel versions
It depends on what features of Excel 2002 are being used and how the code is
structured. The safest way is to do the development in Excel 2000. -- http://www.standards.com/; See Howard Kaikow's web site. "tom" wrote in message ... is there another way then creating the macro in the older excel version? this takes tooo long (e.g. siable the feature in excel 2000? -----Original Message----- You need to eliminate the use of features of Excel 2002 VBA not supported by Excel 2000 VBA. One way to do this is to develop the code using Excel 2000, instead of Excel 2002. -- http://www.standards.com/; See Howard Kaikow's web site. "Tom" wrote in message ... Hi all, When trying to run a macro, created in excel XP, on a pc with excel 2000 installed, the macro will find codes that are not recognized in the older excel versions and therefore not finish running. Is there any (simple) coding available to avoid these problems from happening? Thanks, Tom . |
VB code needed for running newer excel version macros in older excel versions
He could program around them, by isolating the 2002 code in modules that do
not get called when the code is run in Excel 2000, but that can be tricky and does depend on how the code is structured. This would eliminate the run-time errors, but the compile errors would still occur. Cleanest way is to develop in Excel 2000. -- http://www.standards.com/; See Howard Kaikow's web site. "Tom Ogilvy" wrote in message ... there is no difference in formats since xl97. Getting the compile errors is what he is getting now. He wants some automatic way to fix them - I don't believe there is a way to do that. -- Regards, Tom Ogilvy "Keith Willshaw" wrote in message ... "tom" wrote in message ... is there another way then creating the macro in the older excel version? this takes tooo long (e.g. siable the feature in excel 2000? Just do a save as into Excel 2000 format and open Excel 2000 , you should get the errors when you compile It that doesnt work export the code modules from 2002 and load em into 2000 Keith |
All times are GMT +1. The time now is 02:21 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com