N
nick
I am writing a SQL server table and Ole Jet dbf table. They are in a SQL
transaction. However, writing dbf file (on network driver) sometimes halts
and I must close the browser (or in VS.Net when debug). After that, the
table lock of SQL server remains. I must go to SQL enterprise manager to
manully kill the process.
Looks the problem is caused by a started transaction termination without
commit or rollback. Any way to make SQL Server automatically release lock
(or roll back) after a period of time if the application is killed in the
middle of transaction?
btw, how to make OLE db dbase quit if network driver of the dbf files has
problem?
transaction. However, writing dbf file (on network driver) sometimes halts
and I must close the browser (or in VS.Net when debug). After that, the
table lock of SQL server remains. I must go to SQL enterprise manager to
manully kill the process.
Looks the problem is caused by a started transaction termination without
commit or rollback. Any way to make SQL Server automatically release lock
(or roll back) after a period of time if the application is killed in the
middle of transaction?
btw, how to make OLE db dbase quit if network driver of the dbf files has
problem?