>How do you trap an error generated by SQL server in Visual Foxpro 6.0 when there is a problem connecting to SQL server so Foxpro error handling routine will catch it before SQL throws a message box on the user's machine with an error. For example, Connection Failed because of SQL Server Error 18456 or Error 4060. Help please.....

See A sure fire way to prevent the odbc driver from popup ? Message #517180.