>If NT detects no activity of the connection, it will notify SQL Server. SQL
>Server will then terminate the connection and rollback the current transaction.
>
What time frame are we talking about? Five, ten, fifteen minutes, etc....

I checked on our SQL Server and it's configured with "remote conn timeout" @ 10 min. However, when I ran a test, canceled it in the middle of the process, and let the connection idle for about 15 min., then used ISQL/W to query on the records. They appeared to be locked and unavailable. BTW, I'm the only one who's using this database.

I then SQLDISCONNECT() to free those records and found out that SQL did not rollback those record updates I made prior to cancellation, which was before the code where it does SQLCOMMIT/SQLROLLBACK. How come?