Method to synchronize data in a Notes database similar to a relational database.
Original Publication Date: 2001-May-01
Included in the Prior Art Database: 2003-Jun-18
Disclosed is a method to help synchronize data between documents within a Lotus Notes database. Lotus Notes is not a relational database, and therefore suffers from lack of relational capability. Different document types that may need to keep the same data information (such as Employee serial number, dept, etc.), may exist within the database. This data must exist in both documents, rather than only in one document that can be referenced by the other as would exist in a relational database. When someone changes the value in one document, the other document will still have the old value, unless it is also manually changed (since 2 distinct copies of the same information exists). When many data elements need to be shared, and the dynamics of allowing them to change value exists, keeping information synchronized across documents that share information within Lotus Notes becomes very difficult, and usually requires manual intervention. This publication documents a Lotus Notes Agent that gets executed dynamically whenever a change occurs in a single field (such as project name in Table B). It automatically locates and updates every relevant document in the database application that references that field, to ensure the changes are propagated to the dependent documents as well. The example Lotus Notes Agent script can easily be changed to be adopted to other documents and document types within any Notes database. This relieves some of the burden from the users and the administrators of the database with data synchronization problems in complex applications.