This may be old news to some of you, but it was a surprise to me.
After Rick Martin’s eye-opening CIDC 2020 presentation on preventing SQL disconnections I was stoked and immediately implemented the technique in one of my NetTalk web server apps that occasionally hung.
Fortunately, for testing I was running the web server manually rather than as a service. So when it choked a few hours later, I was able to see the error window (pic).
In that I use Capesoft’s Message Box to hook Stop and Message windows, I was surprised to see the app sitting on this window cheerfully willing to wait forever for a click on the OK button.
TL;DR much experimentation revealed that either setting {PROP:LogonScreen}= FALSE or including the driver option /LOGONSCREEN=FALSE in the table definition in the dictionary suppresses that window from appearing.
I did not know that.
Now my app can recover from a momentary Disturbance in the Force.
I did a little show-and-tell in the ClarionLive open webinar on 9/23/2020 https://www.youtube.com/watch?v=kAm-ntxBQ84
Did I say, BTW, that Rick’s approach is brilliant?
jf
