human Posted October 18, 2023 Share Posted October 18, 2023 (edited) I have a solution that relies on an OBBC (mysql) data source. What's the best way to trap if that data source is down? In my tests, with it down, as soon as I try to open the connected solution or run a script from that solution, it opens the Find In Progress... dialog, and there is a long delay before that stops, and that's what I would like to avoid. I would like to immediately get a message to the user that the ODBC source is down, rather than having to wait for a find and then trapping for an error. Also, it seems that Get(LastError) comes back as zero for "Data Source Missing", which is strange. Edited October 18, 2023 by human Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now