Could you not just rsTemp.Close after reading the max value?

Yes - I have seen the ADO objects keep information locked beyond the original intent. We had several lockups similar to this one. In our situation, we could use the NOLOCK because we were not updating that information.

Guarddata-