Probably all you need to do is to just make sure you close your connection in your catch:
Catch loError As Exception
oApp.cError = oApp.ErrorSetup(loError, oApp.Debug(cSQL))
oConnection.Close()
End Try
~~Bonnie
>I am not sure if this is related but since last night I am adjusting a SQL Insert syntax to add all the required fields in order to avoid the null error message. So, as long as all those fields are not added, I am getting this error. So, I suspect that because the error occurs on the SQLExec() command that it gets stuck in memory. In such circumstances, what should I do to make sure this is all cleaned up?