Re: Forms6 - selective access to a field depending on a global variable value

Thanks, we'll give that a go as there will be 8 fields that are either editable or not depending on the variable

"Daniel Morgan" <dmorgan_at_exesolutions.com> wrote in message news:3D650131.D39B9D82_at_exesolutions.com...
> Sally Pearce wrote:
>
> > Found it - 'set_item_property'.
> >
> > (RTFM,rtfm,rtfm,.... but first FINDtfm!)
> >
> > "Sally Pearce" <sally.pearce_at_ncr.com> wrote in message
> > news:3d64ed2a$1_at_rpc1284.daytonoh.ncr.com...
> > > Forms 4.5 Oracle 7.3.4 (yes, I know this is StoneAge stuff, but we
will be
> > > moving to the Bronze Age shortly - Forms6. The date for moving into
the
> > > Steam Age 8.1.7 is somewhere in 2003 . . .)
> > >
> > > The problem is this: how do we set up form attributes in such a way
that
> > the
> > > users can enter and update some fields on the canvas only if a
particular
> > > global variable is true?
> > > We to prevent the user entering the fields and trying to update them
if
> > the
> > > variable is false, but allow them to update if the variable is true.
> > > We can see that you can set the canvas attributes 'updateable' to true
or
> > > false, but can't see any way to do this conditionally.
> > > We know that we can use triggers (when-validate-item) to warn the
users
> > > after the fact, we have also tried the on-mouse-enter trigger but this
> > > prevents the user moving the mouse over the form field to fileds
beyond
> > this
> > > point.
> > >
> > > Is there a way to do what we want? I'm sure there must be (I
couldn't
> > find
> > > anything on Google)
> > >
> > >
> > >
>
> Exactly. Another way is to put the editables in one block, the
non-editables in
> a separate block and build a 1:1 relationship between them. Then you can
set the
> block property affecting all of the fields in a single statement rather
than
> having to write code to do so on an item-by-item basis.
>
> Daniel Morgan
>
Received on Fri Aug 23 2002 - 13:34:32 CEST