If a lnHandle=SQLCONNECT("SomeDB") fails, the SQL Server ODBC driver pops up a nice little screen, giving the ability to retry.

Very cute, but in a huge installation with 100+ servers running some VFP-program unattended, this is not very practical, because the program in effect stops, and nobody'll notice it.

I'd like to handle this situation by simply writing the errror info obtained with AERROR() into the event log and gracefully exit the application.