Force ADODB Connection.Errors to throw or alert in VB?
<p>The most subtle errors will often hide inside an <code>ADODB.Command</code> object.  In VB and ASP, by default, if you don't explicitly check the <code>.Errors</code> property, you nothing will tell you that something has gone wrong with the database.</p>

<p>Having just discovered this, and having a large codebase with hundreds of ADODB calls: Is there any single setting that can cause these Command objects to throw a server error?  Or do I really have to wrap or append every ADODB operation in a <code>IF cmd.Errors ...</code> check?</p>