I don't think you have thought that through at all, the approach is widely
used particularly for large addins, never mind.

As for your other post, look at Application.AltStartupPath

Another thing you could do is put shortcuts to your addins in a/the startup
folder.

Best approach is rethink along the lines suggested.

Regards,
Peter T

"Maury Markowitz" wrote in message
...
On Feb 18, 3:05 pm, "jaf" wrote:
Peters suggestion would probably work best. Even better if located on a
network server.

No, this is TERRIBLE. If there is any problem, even temporary, with
the network the macros just stop working. No error like "lost
connectivity" or such, no, function calls simply report "remote
machine cannot be found". This is precisely the problem I am trying to
avoid by using XLSTART.

Furthermore, using a startup script in the wb is both slow and error
prone. For instance, if I e-mail the file to someone, there's no
guarantee it will work. Even if all you do is load the AddIn from a
local directory instead of a network one, opening Excel from another
app, like Access, fails to load the modules.

Maury