> On Mar 8, 2017, at 9:09 AM, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > Currently, let's say a user begins a transaction and the new record gets > the sequence number. Before that transaction is completed another user > starts a new record (or that user starts another process to create another > record) - and gets the same sequence number. The first one to save wins.
This is not true if you are using 4D's Sequence number function. As long as you create a new record (or duplicate one) other processes will get a different sequence number. I have used this function for years (decades? yikes) without problems. The most likely issue is a programming mistake. You need to be sure that a new record (or duplicate) is created when assigning the sequence number. John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
