Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have Excel 2003 available. Some of my users may have Excel 2002 or
even 2000. I have the following libraries references in the VBA project for this workbook: -- Visual Basic for Applications -- MS Excel 11.0 Object Library -- OLE Automation -- MS Office 11.0 Object Library -- MS Forms 2.0 Object Library -- MS Scripting Runtime Will Excel automatically pick up the correct library reference when the other user opens it? If not, how do I make sure the correct library gets attached? Are there any other libraries I'm likely to have problems with? Ed |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Ed,
You shouldn't have any problems supporting Office 2002 or 2000 as long as you don't attempt to use any features that were added in a later release than the user will have on a machine. Thus, as long as you stick to features that were present in 2000, the code should work for all your users. -- Cordially, Chip Pearson Microsoft MVP - Excel Pearson Software Consulting www.cpearson.com (email on the web site) "Ed from AZ" wrote in message ps.com... I have Excel 2003 available. Some of my users may have Excel 2002 or even 2000. I have the following libraries references in the VBA project for this workbook: -- Visual Basic for Applications -- MS Excel 11.0 Object Library -- OLE Automation -- MS Office 11.0 Object Library -- MS Forms 2.0 Object Library -- MS Scripting Runtime Will Excel automatically pick up the correct library reference when the other user opens it? If not, how do I make sure the correct library gets attached? Are there any other libraries I'm likely to have problems with? Ed |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Thanks, Chip. I appreciate the boost.
Ed On Aug 29, 12:43 pm, "Chip Pearson" wrote: Ed, You shouldn't have any problems supporting Office 2002 or 2000 as long as you don't attempt to use any features that were added in a later release than the user will have on a machine. Thus, as long as you stick to features that were present in 2000, the code should work for all your users. -- Cordially, Chip Pearson Microsoft MVP - Excel Pearson Software Consultingwww.cpearson.com (email on the web site) "Ed from AZ" wrote in glegroups.com... I have Excel 2003 available. Some of my users may have Excel 2002 or even 2000. I have the following libraries references in the VBA project for this workbook: -- Visual Basic for Applications -- MS Excel 11.0 Object Library -- OLE Automation -- MS Office 11.0 Object Library -- MS Forms 2.0 Object Library -- MS Scripting Runtime Will Excel automatically pick up the correct library reference when the other user opens it? If not, how do I make sure the correct library gets attached? Are there any other libraries I'm likely to have problems with? Ed- Hide quoted text - - Show quoted text - |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Terminating autofilter removes commandbuttons (xl2000, not in xl2003) | Excel Programming | |||
xl2000 vs. xl2003 RangeFromPoint and Grouped Shape | Excel Programming | |||
Library issues | Excel Programming | |||
veryhidden with xl2000 & xl2003 | Excel Programming | |||
Performance trouble when changing from XL2000 to XL2003 | Excel Discussion (Misc queries) |