Sequence numbering on a single server

View member feedback to this tip.

I've looked at all the sequence number generators and they are either specific to a version or have many design elements. To avoid any duplications, I use the session.saveddata class property. When called and used from an agent, it will produce sequence numbers that never duplicate, even if run off a server or local client.

How to use this class property: Create a hidden manually run agent and place this script in the initialize.

Code

MEMBER FEEDBACK TO THIS TIP

This code should be used very carefully: "SaveData" document is deleted and recreated each time the appropriated agent is resaved. Therefore, the counter would be reinitiated each time you update the database's design.

-- Aleksei S.

******************************************

The code here is fine for coming up with "A Number" but runs the risk of generating multiple duplicate numbers if more then one user goes for a number at near the same time.

The big problem is that writing and reading takes time and there are no checks available to tell you if someone is reading/writing or what they are doing. The only workaround I've ever found for avoiding duplicate numbering in multi-user situations is a technique I cal

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 Lotus Notes Domino Agents Run or restart Notes/Domino agents via text messages Calculating results for a column in a Lotus Notes view Approve Lotus Notes documents using a BlackBerry mobile device LotusScript agent indexes Lotus Notes/Domino databases Top 10 Lotus Notes/Domino coding and development tips of 2008 Open documents in Lotus Notes from the Web without a UNID Fix and update Lotus Notes documents with limited access Verify scheduled agent status with Domino Extensible Language (DXL) Top 10 Lotus Notes Domino programming and development tips of 2007 How to export data from a Lotus Notes database to a CSV file

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

l "Who's got the Mike." The idea is highly simplistic. You create a document I call a control document.

It exists alone and has an author field. This document represents the "Mike." When no one is generating a unique number the author field contains an asterisk (*) which means anyone can have it. When a user needs a unique number the code "tries" to place that users name in the author field of the control document and save it. If they succeed in saving the control document then they had editor access to the control document and they, "Have the Mike" and can make a new number.

Anyone else trying to generate a number now will be blocked because they can't save their name in the author field of the control document. They have to wait. Once the system has generated the new number and recorded that fact for future number generation, the control document is populated with an asterisk and saved -- thus allowing anyone else to grab it and create a unique number.

This approach is as close as I've ever come to assuring unique numbers in multi-user applications where more then one user could attempt to get a unique number at the same time. Only one person can own the control document at any time.

—John G.

Do you have comments of your own? Let us know.