October 18, 20232 yr 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, 20232 yr by human
Create an account or sign in to comment