I currently have 17 add-ins loaded. Can that be right? Let me count again. Yep, seventeen. Six of the add-ins live in
C:\Documents and Settings\Dick.NEBRASKA\Application Data\Microsoft\AddIns, which is the default location for add-ins on my machine. There are a couple that live elsewhere on my local drive. It all boils down to eight add-ins that are on network shares.
Putting add-ins on network shares rocks. I can install the add-ins on client machines around the office and be sure they’ll always be running the latest version. I like the method from a deployment perspective, but there’s a problem. When I’m traveling and start Excel, it complains. To wit,
\NetworkShareMyaddin.xla could not be found. Check the spelling of the file name, and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted.
Yeah, that makes sense. I’m not connected to the network, so it can’t load the add-in. If I’d put those add-ins on the C drive, no problem. A few of them write to a database on the server, so they wouldn’t do any good locally anyway. If it is was one add-in, I would probably just ignore the error. But with eight add-ins, it takes a long time for Excel to load and it wastes precious airport battery life. I’ve come up with these four alternatives:
- Live with the slow load times when not connected.
- Move the add-ins to the C drive on all the client machines and code something that checks the version against the server. This way I could let users know when a new version is available.
- Code something that loads the add-ins dynamically depending on the availability of the network. It would be like a master add-in that loads all of the other add-ins. This would also simplify my menu problem
- Ask the super smart readers of DDoE what they think.
I’ve chosen #4.