I found the issue. Plain copy-control mistake. He changed the add-in default
directory on his copy to another location, so it was not accessing xla file.
Thanks for the response though. Really appreciate it.
Mike
On Wed, Jan 12, 2011 at 9:22 PM, Paul Schreiner wrote:
> It's been a while since I
It's been a while since I played with Add-ins...
But the last time I did, I discovered that when the user opens the .xla file,
it
makes a "local" copy.
But, the trick is that... if the user has Excel open, it has
the add-in open.
If you send him an update, it does not overwrite the local file,
