I plan to distribute Excel apps in LAN. The apps on the file server
should be accessible from work stations. What would be the best way to
include user xla add-ins. I would prefer to store the add-ins to the
server, to enable me to update them without the trouble to reinstall
them in each workstation.

I have tested one solution, which seems to work: Each application
consists of a list of required add-ins including server path and a
routine which installs and loads them on opening, and unloads before
closing the app. Not yet tested with UNC path.

Ideas appreciated
Håkan

hbj used his keyboard to write :
I plan to distribute Excel apps in LAN. The apps on the file server
should be accessible from work stations. What would be the best way to
include user xla add-ins. I would prefer to store the add-ins to the
server, to enable me to update them without the trouble to reinstall
them in each workstation.

I have tested one solution, which seems to work: Each application
consists of a list of required add-ins including server path and a
routine which installs and loads them on opening, and unloads before
closing the app. Not yet tested with UNC path.

Ideas appreciated
Håkan

I've done this before on a corporate LAN and the only issue I found was
that when the addin is first installed via the Addins dialog on the
workstation Excel prompts the user to copy it to a location on that
workstation. DO NOT DO IT! This way the addin is always stored/run from
the UNC path, making it easier to maintain there rather than having to
update every workstation on the LAN.

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

On Dec 29, 8:35*pm, GS wrote:
hbj used his keyboard to write :

I plan to distribute Excel apps in LAN. The apps on the file server
should be accessible from work stations. What would be the best way to
include user xla add-ins. I would prefer to store the add-ins to the
server, to enable me to update them without the trouble to reinstall
them in each workstation.

I have tested one solution, which seems to work: Each application
consists of a list of required add-ins including server path and a
routine which installs and loads them on opening, and unloads before
closing the app. Not yet tested with UNC path.

Ideas appreciated
Håkan

I've done this before on a corporate LAN and the only issue I found was
that when the addin is first installed via the Addins dialog on the
workstation Excel prompts the user to copy it to a location on that
workstation. DO NOT DO IT! This way the addin is always stored/run from
the UNC path, making it easier to maintain there rather than having to
update every workstation on the LAN.

--
Garry

Free usenet access athttp://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

Thank you Garry for your quick reply!
One more question - as you have done this before...
Is it possible to use UNC path (\\myserver\addinpath\myaddin.xla) in
the script to refer to the add-in to install and load? At the moment I
have no server available on which I could test. And, would it require
r/w access or only read access to the server path.

--
Håkan

hbj presented the following explanation :
On Dec 29, 8:35*pm, GS wrote:
hbj used his keyboard to write :

I plan to distribute Excel apps in LAN. The apps on the file server
should be accessible from work stations. What would be the best way to
include user xla add-ins. I would prefer to store the add-ins to the
server, to enable me to update them without the trouble to reinstall
them in each workstation.

I have tested one solution, which seems to work: Each application
consists of a list of required add-ins including server path and a
routine which installs and loads them on opening, and unloads before
closing the app. Not yet tested with UNC path.
Ideas appreciated
Håkan

I've done this before on a corporate LAN and the only issue I found was
that when the addin is first installed via the Addins dialog on the
workstation Excel prompts the user to copy it to a location on that
workstation. DO NOT DO IT! This way the addin is always stored/run from
the UNC path, making it easier to maintain there rather than having to
update every workstation on the LAN.

--
Garry

Free usenet access athttp://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

Thank you Garry for your quick reply!
One more question - as you have done this before...
Is it possible to use UNC path (\\myserver\addinpath\myaddin.xla) in
the script to refer to the add-in to install and load? At the moment I
have no server available on which I could test. And, would it require
r/w access or only read access to the server path.

I'd use..

sFilename = ThisWorkbook.Path & "\AddinToOpen.xla"

...and make sure all the other addins opened by the main addin are
stored in the same folder as the main addin. This way, it still works
if you decide to relocate/rename the unc folder.

Also, you might not need to actually use XLAs for the sub-addins
because you can save workbooks hidden with their IsAddin property set
to 'True' (similar to what John Walkenback does for his PUP utility
addin which opens/closes files as required when menuitems are clicked).
I use addins with my main addins that work like 'Plugins' that enhance
a core addin app with user-specific features. These are XLAs usually,
but not always. These 'Plugins' are stored in the app XLA's folder and
the app XLA uses ThisWorkbook.Path as described above.

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc

Correction:
My 'Plugins' are stored in "Drive:\AppFolder\Plugins" and the apps just
iterate that folder to open each file found there. Usually it's just
one file but I have had occasion to use more than one depending on user
permissions to access extra features.

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc