~Maria BrevelusonakoiJan 29, 2014, 4:44 PM20 PostsAnyone seen this before and know when this will be fixed?
~Fred AsatumiburyndsJan 29, 2014, 5:38 PM107 PostsSeen this before, but doubt it will ever be fixed.The same happens when lots of new documents are created in short time. It's related to the anatomy of Note IDs; see: http://www-12.lotus.com/ldd/doc/tools/c/6.5/api65ug.nsf/85255d56004d2bfd85255b1800631684/00d000c1005800c985255e0e00726863 For UNIDs and OIDs to be unique, the interval of time between two documents being created or a specific document being saved must never become shorter than one tick of Notes' internal clock. Since current computers are able to create and save documents much faster, Notes advances its internal clock to force unique UNIDs and OIDs. It's a huge kludge, let's face it. But since the whole concept is so fundamental to Notes, I doubt this will ever be fixed. Just my 2 cents...
~Emile MinfookonyjipJan 15, 2015, 8:03 AM28 PostsAnd if I may ask, what is your code trying to achieve ?For a - lets say - business or user perspective ? By the look of your code, it sounds as you are trying to invent some kind of Locking mechanism.
~Maria BrevelusonakoiAug 3, 2018, 7:40 PM20 Postsresponse to PeterI wrote this code only for the purpose to show that when many writes occur all at once that the time/date will go into the future. It has no other purpose. Thanks to all responses.