I agree. I've seen posts from people who implemented their database locking logic based on the local/remote connection modes of their data clients. The database should not care what connection mode the database client is operating in. So your database locking/unlocking logic shouldn't concern itself with such things. Now if the data client code wants to call lock & unlock differently based on the connection mode, that's fine... but probably un-needed and creates more code to test, maintain, document and risk introducing bugs.
posted 17 years ago
Thanx guys, for the advise. It seems like I should do lock/unlock no matter whether I am using local client access or networked access - for simplicity sake!
Story like this gets better after being told a few times. Or maybe it's just a tiny ad: