On Fri, Sep 28, 2012 at 9:34 AM, Bob Sneidar <b...@twft.com> wrote: > What I learned from an old multiuser accounting program was to maintain some > kind of >counter column, incrementing it (or resetting it when it gets to the highest >value) >whenever an update occurs. Before the write, but after you lock the table for >updates, >check the value against what it was when you read it. If it's not the same, >someone else >updated it first, so reset the data.
my current plan is actually tw extra columns, one to identify Who wrote the record, and the other for a timestamp. I suppose I'll also sets a time that the lock applies for, and automatically release and one that user when time is up. -- Richard E. Hawkins, Esq. (702) 508-8462 _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
