Re: Record-Locking



Sprinks wrote:
- Are the settings of the Default Record-Locking Strategy and the Open
Databases Using Record-Level Locking fields in Tools, Options, Advanced
specific to a database or to each station's Access installation?

They're specific to each database application. But here's the caveat:
whatever "open database" record level locking setting the first user uses to
open the app is the setting all other subsequent users who open the database
are going to use, regardless of their own setting. This setting is kept
until the last user exits the database.

- If each user is using his own copy of the front-end file, linked to the
same back-end, does that mean record-locking is not employed at all, since
they are not actually opening the same database?

Good for you! That means you already know the importance of split databases,
so you're going to deploy your app with a minimum of hurdles. Make sure that
you keep a persistent connection to the back end open to keep back end
operations as quick as possible.

Record locking is still employed, but the record locking setting in the front
end affects tables in the front end only.

--
Message posted via http://www.accessmonster.com

.



Relevant Pages

  • Re: MS Access already opened exclusively error
    ... I also had default record locking ... MDB file, which is shared on one of the machines. ... The database does not use Access ... do not seem to be caused by any specific thing that my app is doing. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Recordset code
    ... Default record locking: All Records ... Open databases isng record-level locking IS checked ... >> users opening a single mdb file across a network. ... >> issues of database corruption. ...
    (microsoft.public.access.formscoding)
  • Call Center multiuser record locking
    ... I want to build a database to store the 2,000 some members we ... network, this weekend. ... lock records so that only one caller can lock a name and create a call ... Record Locking set to 'Edited Record' ...
    (microsoft.public.access.tablesdbdesign)
  • Re: How to avoid users pick same case
    ... I am using ADO and Access database which is located on the ... One approach is "pessimistic" record locking - locking the record when the edit ... Another is "optomistic" record locking - allowing two users to beginning editing ... It really depends on how likely conflicts are. ...
    (microsoft.public.vb.general.discussion)
  • Re: Record Locking for Editing.
    ... Access don't support Pessimistic Record Locking for Editing ... when the backend database is not the JET database engine (ie., ... user is updating a record and if second user tries to update same record i ...
    (microsoft.public.access.modulesdaovba)

Loading