Need help understanding record locking...

Discussion created by deanchampeau on Aug 15, 2012
Latest reply on Aug 16, 2012 by Malcolm



Most of my development so far has involved solutions (apps?) that are either single-user or are used by a small number of people. I've never had to worry much about users stepping on each other's toes by trying to edit the same record simultaneously. However, I'm now building a solution that will use scripts that edit a parent record as well as records in child and grandchild tables. The likelihood is pretty high that, without some scheme to prevent it, my scripts will break, resulting in all kinds of damage to my solution's data integrity. Can anyone point me in the direction of a best-practices tutorial regarding this issue, or offer me some tips about how to go about this?


Thanks for listening!