|
BTW, if you do decide to use the timeout "feature", just remember to consider the angry phone calls you'll get when a user does take that coffee break, comes back just before the timeout occurs and starts keying in information and, before s/he has a chance to press Enter, BAM - timeout. Because the timer does not recognize keystrokes, just function keys (including Enter). Based on the problem you are trying to solve, I would advise you to consider the no-lock alternative that others have suggested. A bit more coding no matter how you decide to do it. db > -----Original Message----- > From: rpg400-l-bounces@xxxxxxxxxxxx / Andy Hautamaki > Sent: Thursday, October 07, 2004 11:22 AM > > Hi Jonathan; > > No. Its to do with a display file. A user is in a maintenance program and > for whatever reason is inactive in that application for 'x' amount of time > and has a record locked. (Goes for coffee, lunch or whatever) In the > meanwhile other applications are trying to grab that record and are > repeatedly trying to access the record. (Record lock, retry, record lock > retry, etc etc) <snip>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.