I have not noticed that at all. And, you are timing far more than
the connection.Open. Are you sure that is where the slowness resides?

Signature
Robbe Morris - 2004-2006 Microsoft MVP C#
Earn money answering .NET questions
http://www.eggheadcafe.com/forums/merit.asp
It us undoubtably the connection open as I have timed that bit independantly
as well. I added the code to ensure that the connection was really open in
both cases.
> I have not noticed that at all. And, you are timing far more than
> the connection.Open. Are you sure that is where the slowness resides?
[quoted text clipped - 31 lines]
> > Thanks in advance
> > Peter
Peter Chapman - 05 Apr 2006 11:49 GMT
After two days of hell I have finally solved this one.
It turns out that the cause of my problems stem from the windows firewall
being on on the server computer. It apears that my code was hanging while it
waited for the tcp/ip to timeout before it gave up and decided to use named
pipes. I guess 2.0 must try tcp before named pipes - I'm surprised this
isn't documented anywhere though!
> It us undoubtably the connection open as I have timed that bit independantly
> as well. I added the code to ensure that the connection was really open in
[quoted text clipped - 35 lines]
> > > Thanks in advance
> > > Peter