File Already Exists (custom addin problems)

[hatman]

So I have a fair number of cutom addins on my computer... some created by me, others I have downloaded. In the last week or so, I have started getting an error that I can't track down. During Excel initialization, I get what looks like a Msgbox: title = Microsoft Visual Basic, Prompt = File Already Exists, style = vbokayonly. It only shows up when opening one of my custom Addins, which causes that Addin to fail to load. The first bizarre thing is that this behaviour does NOT occur every time that I open Excel... usually every second, but sometimes I might be able to open successfully as many as 5 or 6 times before it happens again. The second bizarre thing is that I added a STOP command at the beginning of the workbook_open event so I could step through in debug mode, only to find that the error and failure occurred before any code was executed... just to prove this to myself, I deleted the entire workbook_open event from the module, and restarted... sure enough, this error seems to occur indpendent of code EXECUTION of the addin. Unless I am completely missing something here. It almost seems like there is a coflict between addins... but it's manifesting itself in a way that I can't track it down.

After having unintalled my own custom addins one at a time, I was not able to conclusively figure out where the conflict lies... by the time I got them all re-installed, the problem seems to have ceased. But I have no idea why. Many of these Addins have been distributed throughout the company, so I feel like I need to figure out the cause before other people start reporting issues that I need to fix. Has anyone seen behaviour like this before?

 

[Legacy 98055]

Did you check for any orphaned instances of Excel running by way of the Task Manager?

 

[hatman]

Yup, that was one of my fist checks... no dice.

 

[Legacy 98055]

Sorry Hat. I have nothing to add here. Am as clueless as you are.

 

[hatman]

Quite alright: this is obscure enough (and I have little enough data to describe the problem) that I didn't really expect much anyway. Thanx for thnking about it, anyway.