Re: Generically Handling Record Locks in *PSSR

[David Wright <opendave@xxxxxxxxx>]

Valid point.  We have also been specifying fields to update in all new
development.  It does not avoid the potential for locks, but does ensure
that the Terms Code Maintenance does not accidently overwrite the Zip Code.

More often than not, if a record is locked long enough to cause another
program's CHAIN to fail, then the original locking program was poorly
written to begin with.  Luckily I never write bad code, so I only have to
fix mistakes coded by others.
On Mon, Jan 19, 2009 at 4:16 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

> (You really only care about the fields you can update, not all of the
> fields. If Sally changes the zip code and Betty changes the credit code
> then there is no conflict.)