When PRO IV cannot communicate with SQL Server, or there is a datatype mismatch or any other SQL error, PRO IV halts the session and requires user intervention. I need to run a batch job that uses SQL tables, but do not want it to halt my overnight processing if there is an error. Is there any way to trap the SQL 366 error so that it doesn't halt the session? Has anyone had any luck with this?