clUnknown is not clear value

halenpolen · Post by **halenpolen** » Sat 30 Oct 2010 13:55

Hi i used this demo
Demos\Win32\Miscellaneous\FailOver,

when I open tquery,kill session,then I moved cursor quMaste to the next record,
Tuniconnection call ConnectionConnectionLost Event
But the value ConnLostCause always set to clUnknown ??
is it a bug?? Can Devart team change it to clRefresh . Because clUnknown is not clear value Thx

AlexP · Post by **AlexP** » Tue 02 Nov 2010 11:01

hello,

Please specify your database name.
Also please check of the value the ConnLostCause variable after executing the following operations: open, refresh, etc.

halenpolen · Post by **halenpolen** » Tue 02 Nov 2010 13:56

[quote="AlexP"]hello,

Please specify your database name.
Also please check of the value the ConnLostCause variable after executing the following operations: open, refresh, etc.[/quote]

MSQLSERVER 2008,
I set quDetail.Options.LocalMasterDetail:=false;
I tried to move next record table master, to see table detail (refresh the table detail with move cursor the master) ,
but when I debuging the value ConnLostCause is clUnknown

AlexP · Post by **AlexP** » Wed 03 Nov 2010 14:24

Hello,

We have reproduced the problem.
It will be fixed in one of the next builds.

bork · Post by **bork** » Tue 16 Nov 2010 10:33

Hello

We fixed the Datail dataset refreshing after connection loss in the LocalFailover mode. This fix will be included in the next UniDAC build.