>A VFP application, using ODBC, looses connection after a while. This could be related to the fact that there is a problem with the database server, network, restart of servers, etc. But, when it happens, it triggers a dialog on the console. And, there is a Try/Catch in the code. But, this is not intercepted by the Try/Catch. The dialog has priority. Anyone would know how to avoid that and catch it in the code?

If I'm looking for reliability I have connections open only the bare minimum amount of time needed to communicate with the backend. It used to be expensive to frequently connect and disconnect like that, but my understanding is modern versions of RDBMSs cache or pool connections so there's not much impact.