How do I simulate an auto-increment field in a Domino database?

How do I simulate an auto-increment field in a Domino database?
Because of the distributed nature of Notes applications, where you can have different replicas on different servers or even on a user's local hard drive, assigning a unique sequential number as a document is being composed is not as straightforward as in a single-server, relational environment. This topic has been discussed extensively in the Notes 4 & 5 forum on LDD. Go there and search for "sequential numbering" and I think you will find dozens of solutions, applicable to different situations.

Download this free guide

Download: IT Certifications 101

Inside this exclusive essential guide, our independent experts break down which IT certifications are worth your time and effort, and how to get started obtaining them to further your career— including specific certifications that any cloud or desktop pro should seriously consider.

Start Download

• Corporate E-mail Address:

  You forgot to provide an Email Address.

  This email address doesn’t appear to be valid.

  This email address is already registered. Please login.

  You have exceeded the maximum character limit.

  Please provide a Corporate E-mail Address.

• • I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.

  Please check the box if you want to proceed.

• • I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.

  Please check the box if you want to proceed.

By submitting my Email address I confirm that I have read and accepted the Terms of Use and Declaration of Consent.

Incidentally, in my experience designing Notes applications, I've found that very often a requirement initially stated as a sequential identifier, can be satisfied with a value that's not sequential but merely unique (e.g., using the @Unique function).