I have an SQL sever backend and ADP front end. As I was working along I suddenly got a Message "Connecton failure" on the update of a form. I re-ran the procedure and noticed that even though I had an error trap "On error got to" statement the error occurred on the EXIT SUB line and did not go through the error trap at the bottom of the procudure. I would simply get the message titled "ADP" connection failure. My database use an application role which is turned on when the uses opens the front end app. I noticed after playing around that the ADP will simply try to reconnect on its own if it succeeds it continues or just gives the connection failure message at which point I have to log out and back in. PROBLEM:
1. How do I trap a run-time connection failure
2. If ADP is trying to re-connect on its own, I would imagine that it is not calling the TurnOnAppRole which I have when the users opens the dB. This would allow the user to cintinue in the dB not under the control of the app role I would think - this is bad.
3. How can I know the status of the ADP/SQL connection and App role status during runtime (From the ADP Front End), and if there is a failure try to reconnect and turnon the app role automatically or if that fails give the user a message and log them out.