silence readonly messages
Joe Chasan
joe at magnatechonline.com
Thu Aug 25 07:12:12 PDT 2011
On Thu, Aug 25, 2011 at 10:01:59AM -0400, Craig Tooker wrote:
> On 8/25/2011 09:48, Joe Chasan wrote:
> > when calling clerk on a file with -ro (read-only) flag set,
> > i have processing @key 1/2/3 etc, which determines which version
> > of screen 1/2/3 etc, can be viewed based on a user's security setting.
> > a quick check, then a "switchto" either "1a" or "1b" for example.
> >
> > problem is get the read-only message just from the @key - even though
> > no update or real field setting is done.
> The @entsel runs unlocked, any @key runs in locked (update) mode. The
> trick is to use "goto @key1" from @entsel and at the end of that routine
> use a "goto @entsel. That avoids locking the record (going into update
> mode).
you mean have @key1 execute stuff in @entsel, instead of @key when
record is not locked. i already tried that anyway.
in this case that does not help, in debugging one can see that
@key immediately triggers the message before any processing is executed.
even something like @key1::end: will trigger the message when using -ro
--
-Joe Chasan- Magnatech Business Systems, Inc.
joe - at - magnatechonline -dot- com Hicksville, NY - USA
http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264
More information about the Filepro-list
mailing list