ADO.NET infomessage event not firing when connection is broken

[itp]

Hello,

I have looked at several ADO.NET resources and they all
say to use the infomessage event handler. I have added the
code to my form but when I disconnect the network cable,
it does not fire.

I have also read that infomessage is for server error
messages below 10. I have tested this by creating a stored
proc that raises a custom error of severity 8. When I
execute this, it does fire the infomessage event handler,
so I know that my code works.

But it does not catch broken connections! Inside VB.NET,
the Intellisense mouseover comment says "This value is
reserved for future versions of the product."

Is the "broken" state not supported in ADO.NET?

Anyone else have this issue or any info on it?

Regards

[scorpion53061]

The way I did this was to use the TCPIP control in a seperate thread, do a
loop and report when the connection is unable to complete the loop.

Let me know if you need more help.

"it*@techie.com" <an*******@discussions.microsoft.com> wrote in message
news:02****************************@phx.gbl...

Hello,

I have looked at several ADO.NET resources and they all
say to use the infomessage event handler. I have added the
code to my form but when I disconnect the network cable,
it does not fire.

I have also read that infomessage is for server error
messages below 10. I have tested this by creating a stored
proc that raises a custom error of severity 8. When I
execute this, it does fire the infomessage event handler,
so I know that my code works.

But it does not catch broken connections! Inside VB.NET,
the Intellisense mouseover comment says "This value is
reserved for future versions of the product."

Is the "broken" state not supported in ADO.NET?

Anyone else have this issue or any info on it?

Regards