>>>In our CA implementation we probe the applic.sqlhandle property and if the last time this happened is more than 5 seconds ago, it will check the connection with a SQLEXEC(Applic.SQLHandle, "") in the before.... events. If it fails, it will first try to reconnect, after which if succesful would refresh your records just fine.
>>>
>>>My solution does not get you a new SQLhandle. The old one will just get re-established.
>>>And yes, your updates on a re-vided CA will work just fine. There is no need to refill the CA.
>>>
>>>And no, this is not a newbee question. I don't think there are a lot of even experienced VFP developers aware of this. It was a programmer on Microsofts VFP team posting this solution here on the UT about 15 years ago. I just can't remember the name of that guy. It was not Calvin Hsia or John Koziol though.
>>>
>>The query every 5 secs will clearly not overload any backend, unless a couple of thousand users are connected same time and queries have to filter also a lot of visibility rules - and if it were problematic, you'd time to optimize ;-)
>>
>>Still, reading about it I wonder if this "just grew" or if you considered / tested moving to a push based solution - which of course depends a lot of the amount and frequency of new data added or altered. Or is a discernable amount of 5 sec queries returning info about changes important to the biz case loaded ?
>
>Well, feedback from our clients, some 15 years ago, indicated a lot of broken connections, especially on laptops with crappy WIFI, which rendered our product to be useless on WIFI. I remember posting a question here on the UT about this problem and got an answer from the VFP team. It should be somewhere on the archives here.

Ok thx, crappy WiFi will result in more than crappy push results, while polling will detect and fix ;-)