On Jan 15, 2008 11:43 AM, Aparajita Fishman <[EMAIL PROTECTED]> wrote:
> > I remember during a session of the A4D class a couple of years ago > > that we > > discussed optimistic locking. Was there any code for this that I > > could use? > > It's in the docs in the "Timestamps" section. That's why timestamps > were created. Duh. Sorry about that. I was looking at the command reference, not the timestamp section. Any comments on the choice of invalidating User A's work if B takes the record? The issue I have with this is that B may not even edit the record. Regarless of whether they intend to edit it or open the record and walk away from their screen, A is not allowed to save any of their changes. It seems the favor is in the lap of ANY other user that happens to grab that record. Now granted, for a simple detail screen with a few fields, that may not be an issue, but we are working on saving a session to the db that contains hundreds of variables. Any suggestions for direction? Thanks, Michael Check _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
