Well, I've tested two things to generate errors; first put an incorrect database name in the connection string and second I shut down the SQL Server. In both instances an error occurs when trying a test program, however the error seems to be generated that does not come from Fox - maybe the OS or SQL (I'm not sure). Anyway, an ON ERROR doesn't catch it, it displays a messagebox "Microsoft SQL Server Login ... connection failed...". Clicking "Ok" then opens a SQL Server Login dialog, which will only put our users in a tizzy! How does one trap this error and avoid these messagesboxes and dialogs?