Some co-workers had an application that kept doing this. Two people would browse the same record, and while talking on the phone each would enter their own updates. The second update screwed up the key to the various lines of text for the screen. I suggested, and it worked, that the last update time stamp be placed in the screen, and if it didn't match the updates where thrown away. Stopped messing up the keys.
On Mon, Jun 16, 2014 at 5:47 PM, John Gilmore <[email protected]> wrote: > There is botched arithmetic in my shoes-inventory example. Luckily, > it does not affect the validity of my argument. > > I should have written > > . . . B updates the record to reflect a ccount of 15 [not 20] pairs . . . > > Tom Marchant noted this blunder, and I am grateful to him for making > me aware of it. > > John Gilmore, Ashland, MA 01721 - USA > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
