Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Jon
It works! I put the Application.Run command inside an If statement so that it only executes when in the Excel 2007 environment. In Excel 2003, the statement is not executed, the module containing all the 2007 macros is not compiled, and everything works correctly. Thanks greatly for this advice. -- Don H. "donh" wrote: Jon, This seems like it should work. I appreciate the suggestion; thanks. I'll report back with results. -- Don H. "Jon Peltier" wrote: If you are going to use another workbook, you don't need this complication. However, as I was clicking on this post I was already thinking of a solution, and it also uses Application.Run: Application.Run "'" & ThisWorkbook.Name & '!Excel2007Procedure" This won't cause anything to compile, because does not call the procedure until run time. - Jon ------- Jon Peltier, Microsoft Excel MVP Peltier Technical Services, Inc. http://PeltierTech.com/WordPress/ |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
How to protect excel workbook from macro starting from Developer - Code ribbon? | Excel Programming | |||
Modifying XLA to show toolbar in XL 2003 and ribbon tab in XL 2007 | Excel Programming | |||
Assign a Ribbon Control's Label from a Variable in VBA Code | Excel Programming | |||
Open Workbook Add In with 2007 & 2003, Which Changes Ribbon & Tool | Excel Programming | |||
Splitting up code ribbon | Excel Discussion (Misc queries) |