No, my add-in code is not referencing SQL Server in any way.

What's strange is that the errors occur in operations where the add-in is
not even involved, such as pressing the To... button on a new message.
There is no visibility to this action from an add-in.

I also believe it's either related to the Office XP PIA's or perhaps
something related to the .NET Runtime that is changed when you install SQL
Server. The add-in runs fine on 100's of computers, unless SQL Server is
installed. It's hard to imagine that SQL Server would have any impact on
the Outlook API, so my thought was .NET, but I don't know what SQL Server
changes related to that either.

Are any of the add-in's running at your site built using .NET?

Michael

"Ken Slovak - [MVP - Outlook]" wrote in message
...
I don't know, I have VS 2005 and SQL Server Express installed on a few
machines here with no problems with Outlook addins. Is your addin code
referencing SQL Server in any way?

I haven't tried any addins in a setup like that which use the Outlook 2002
PIA's however, my setups all have the Outlook 2003 and/or the Outlook 2007
PIA's installed.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Michael" wrote in message
...
Well, I isolated it to SQL Server. If you install SQL Server (I
downloaded SQL Server Express for this test), it conflicts with the
add-in, so it has nothing to do with Visual Studio itself. Any ideas
anyone?

Michael