Record locking across servers

You Can View User Feedback To This Tip

The following sample illustrates how to lock a document to prevent simultaneous access by two users and to prevent update of the document on another server when replication has not occurred. In testing in the production environment, this code increased the time to open the document by 0.8 seconds.

Note: If you include the code in a subform, then all you have to do, in any application -- is plug in the subform to have the form be controlled.

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Other Create a dynamic user-driven navigator for a Notes/Domino application How to apply XSL style sheets to XML views Comparing replicas on clustered Lotus Domino servers Creating a Lotus Notes view column categorized by month Using the XMLHTTP object for integration with Domino or any RDBMS back end Hiding field properties/data from DocProperties box Export a view to Excel without coding Prevent document deletion if there are response documents Switching between test IDs quickly AddParameter to a NotesXSLTransFormer

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

Code

A locks database must be created on one server. The lock record should contain the following fields: Document ID, Created By, Originating Server, Date Modified, Expiration, and Current Edit (Yes or No). The expiration date is set two hours from the modification date, the maximum time it takes for replication to occur is two in this environment. The following code should be placed in the Queryopen and the Querymodechange events:

USER FEEDBACK TO THIS TIP