Loading an Addin via Registry (Excel 2000 SP-3)

Topic

New Reply

I set a Registry setting, HKEY_CURRENT_USERSoftwareMicrosoftOffice9.0ExcelOptionsOPEN777 = myaddin.xla(where “myaddin.xla” represents the complete path/name of the addin). I expect that when I start Excel I should see my custom menu entry on the menu bar. My result is that the menu item is missing, although a peek at Tools/Addins shows the addin is available and checked. Any ideas?

Reply | Quote

Replies

How is the menu added?
Is the custom menu created on file open or addin installed?

Steve

Reply | Quote

It’s created upon loading the addin.

Reply | Quote

You can also load the addin through VBA, although this might not be appropriate in your situation. Something like the following should work for the analysis toolpak.

AddIns(“Analysis ToolPak”).Installed = True

If you are coding one specific workbook, and using an addin to update/make changes to the workbook, you might be better going that route.

Reply | Quote

The addin is a suite of Excel tools for a global user base. It is installed from a custom folder, not one of the Office folders, so I can’t rely on it being loaded automatically without setting registry settings, etc. I had assumed that, based on some knowledge base articles, I could simply set the one registry value “OPENxx…”. The addin seems to get loaded by virtue of the fact that it is listed under Tools|Addins…the problem is that the custom menu item added to the menu bar by the addin is not visible unless I manually unload/reload the addin.

Reply | Quote

Got it. In my testing I purposely set the increment for OPEN to a high value so as not to step on some other setting. However, that caused a gap between my setting and the last OPEN setting. Apparently, if there is a gap of even one increment (i.e. OPEN4, OPEN6) the custom menu is not added to the menu bar. Ensuring that all OPEN values are sequentially numbered resolves the problem.

Reply | Quote

Got it. In my testing I purposely set the increment for OPEN to a high value so as not to step on some other setting. However, that caused a gap between my setting and the last OPEN setting. Apparently, if there is a gap of even one increment (i.e. OPEN4, OPEN6) the custom menu is not added to the menu bar. Ensuring that all OPEN values are sequentially numbered resolves the problem.

Reply | Quote

Ethan,

You mention some knowledge base articles – which ones?

Cheers

Reply | Quote

Tim,

Sorry for the late response. I searched the MS knowledge base for info. on the “OPEN” resgistry value for Excel addins. One of the better pages, although geared towards Office 97, is:

http://msdn.microsoft.com/library/default….dn_addins97.asp[/url]

Reply | Quote

Tim,

Sorry for the late response. I searched the MS knowledge base for info. on the “OPEN” resgistry value for Excel addins. One of the better pages, although geared towards Office 97, is:

http://msdn.microsoft.com/library/default….dn_addins97.asp[/url]

Reply | Quote

The addin is a suite of Excel tools for a global user base. It is installed from a custom folder, not one of the Office folders, so I can’t rely on it being loaded automatically without setting registry settings, etc. I had assumed that, based on some knowledge base articles, I could simply set the one registry value “OPENxx…”. The addin seems to get loaded by virtue of the fact that it is listed under Tools|Addins…the problem is that the custom menu item added to the menu bar by the addin is not visible unless I manually unload/reload the addin.

Reply | Quote

You can also load the addin through VBA, although this might not be appropriate in your situation. Something like the following should work for the analysis toolpak.

AddIns(“Analysis ToolPak”).Installed = True

If you are coding one specific workbook, and using an addin to update/make changes to the workbook, you might be better going that route.

Reply | Quote

It’s created upon loading the addin.

Reply | Quote

How is the menu added?
Is the custom menu created on file open or addin installed?

Steve

Reply | Quote

If you check my spot on the Excel MVP page below, you’ll see a number of utilities which have an Excel based setup routine in them (Autosafe, Name Manager, Flexfind, AutosafeVBE). Works without trouble. Their code is not protected (of the setup routines that is).

Reply | Quote

If you check my spot on the Excel MVP page below, you’ll see a number of utilities which have an Excel based setup routine in them (Autosafe, Name Manager, Flexfind, AutosafeVBE). Works without trouble. Their code is not protected (of the setup routines that is).

Reply | Quote