I have a COM Add-In I developed in VB6 that a user had a problem with
recently. The user did some maintenance (undescribed) on his PC and
afterward the Add-in didn't load when he started Excel.

The user re-ran the installer and the add-in still wouldn't show up.
After playing around a while, the only way he could get the add-in to
load was to move it from the Program Files/AppName folder to the
User/Application Data/Microsoft/Addins.

This didn't make any sense to me. It's a registered DLL, not an xla,
xlm, or xll. How on earth would this cause the add-in to load? Any
ideas?

Thanks,
Nick

The user did some maintenance (undescribed)

What one wonders, Administrator Privileges, write access to Program Files or
a certain part of the reg perhaps.

If user has it working in the default Addin location why not leave it where
it works, if necessary moving any other of your files/folders to same path
if necessary.

Whether or not the dll was previously registered, manually selecting it from
the Com Addins menu will do a Regsvr32 in its new location.

Can user uninstall it, move it back to original folder, then manually select
and install from the COM Addins menu.

Regards,
Peter T


"Nick Hebb" wrote in message
oups.com...
I have a COM Add-In I developed in VB6 that a user had a problem with
recently. The user did some maintenance (undescribed) on his PC and
afterward the Add-in didn't load when he started Excel.

The user re-ran the installer and the add-in still wouldn't show up.
After playing around a while, the only way he could get the add-in to
load was to move it from the Program Files/AppName folder to the
User/Application Data/Microsoft/Addins.

This didn't make any sense to me. It's a registered DLL, not an xla,
xlm, or xll. How on earth would this cause the add-in to load? Any
ideas?

Thanks,
Nick