MacroEcon1337
Board Regular
- Joined
- Mar 16, 2017
- Messages
- 64
Situation
I have a modestly complex workbook, with a lot of modules containing custom macros. The workbook also has a customized toolbar which links to a lot of these macros. The workbook is not connected to "linked" to any other workbooks. Most of the macros involve manipulations on the sheets [hiding rows, sorting columns, things of that nature]... but there is a heavy interaction between the macros and named-ranges in the workbook. For example, some of the toolbar buttons reference specific sheets or named ranges that would not exist in other workbooks. [However, the toolbar offers much functionality that is not dependent on workbook-specific named/ranges, but somehow Excel will have to recognize which enviornment it is in: it's native/original workbook, or a new workbook]
Motivations for Migrating to Add-In
I want to migrate the toolbar, and associated library of macros, into an excel-add in. The motivations behind this are: (1) to make the toolbar accessible from any excel document [right now, the toolbar is only accessible from the workbook that has the modules] and (2) to provide a minimal layer of protection to the source code, which is totally exposed.
Other Notes
- Currently working in Excel 2010, but will likely shift to Excel 2016 later in the summer. Would it be better to do the conversion after that?
- Would I want to use a Com Add-in?
- The Toolbar still has value
Any wisdom or suggestions for execution on this topic are greatly appreciated,
MC
I have a modestly complex workbook, with a lot of modules containing custom macros. The workbook also has a customized toolbar which links to a lot of these macros. The workbook is not connected to "linked" to any other workbooks. Most of the macros involve manipulations on the sheets [hiding rows, sorting columns, things of that nature]... but there is a heavy interaction between the macros and named-ranges in the workbook. For example, some of the toolbar buttons reference specific sheets or named ranges that would not exist in other workbooks. [However, the toolbar offers much functionality that is not dependent on workbook-specific named/ranges, but somehow Excel will have to recognize which enviornment it is in: it's native/original workbook, or a new workbook]
Motivations for Migrating to Add-In
I want to migrate the toolbar, and associated library of macros, into an excel-add in. The motivations behind this are: (1) to make the toolbar accessible from any excel document [right now, the toolbar is only accessible from the workbook that has the modules] and (2) to provide a minimal layer of protection to the source code, which is totally exposed.
Other Notes
- Currently working in Excel 2010, but will likely shift to Excel 2016 later in the summer. Would it be better to do the conversion after that?
- Would I want to use a Com Add-in?
- The Toolbar still has value
Any wisdom or suggestions for execution on this topic are greatly appreciated,
MC
