|
-
Jul 28th, 2000, 01:04 PM
#1
Thread Starter
New Member
We are writing a desktop app (VB6) that connects to SQL 7.0 via LAN. The program actually queries the remote SQL database to extract the next most "important" record using an ADO control. I am using a client side cursor and would like for the queried record to be locked so that the 10 other users of the app who are performing the same job, do not query and edit the same "important" record and wreak havoc on the database. Which LockType should I use?
Have I neglected to list any parameters here for proper diagnosis?
I would like to get a little more information about record locking and which LockType to use under different circumstances...all suggestions for more information about it (forums, books, etc.) are welcomed and appreciated. 
thanks,
jason
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|