Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2004

    Unanswered: SQL/Acces Record Locking

    I am running an Access 2000 front end and MS SQL2000 as a backend and I am having problems with record locking.

    I have just found out that If you use ODBC then Access acts as if No Locks are set. In an ideal world I need the record to be locked by a user as soon as they move onto it. If not as soon as they start editing it?


  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    You need to do a little reading about SQL Server impliments locking and the type of locks that exist. I suggest you start with Books Online\Contents\Accessing and Changing Relational data\locking and everything under that chapter.

    Actually holding an exclusive lock on a record for a long period of time is generally a bad thing. Some programmers impliment a record check out scheme through their applications.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Sep 2004
    You can set the locking option the in Access query that you're using. Look in the query properties. Also, do a search on optimistic/pessimistic locking.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts