Hi Eric,
I think that's a realistic approach, assuming write access, but there's a
lot of work to do.
Ensure no running instance(s) of Excel.
Check registry for all xl versions, 9.0 etc (xl97 8.0 has 'Microsoft Excel'
vs 'Options').
Is your xla already in the addins collection. If so is it installed or not,
in a default addins path or elsewhere (different implications), not
installed but in the collection with an entry in "\Add-in Manager" t.b.
deleted with care.
The 'x' in new OPENx will need to be OPEN-max(n)+1 assuming there are no
missing n's between 1 & max(n), or if OPEN* doesn't exist simply OPEN.
The AddinInstall event in your xla won't fire of course.
The above is not a complete list of things to handle.
Regards,
Peter T
"Eric" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> Hello,
>
> I am writing a script (I am using InnoSetup) to distribute and install an
> Add-in automatically. I want the install to be totally transparent for the
> user.
> It looks like I could just add the key OPEN or OPEN1 ,...,OPENx to
> HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Options, but I was
> wondering if someone add something more elegant or simply a better
> suggestion.
>
>
> Thank you.
>
> Eric
>
>
|