Re: forms 4.5 - update user vs view user
Date: 1997/10/13
Message-ID: <01bcd7f2$286ada00$2aaeb6cc_at_dino>#1/1
You may want to have only one form so that it is easy to maintain. There
are two ways to implement it:
(1) use query_only option in the call_form option for users that do not
have privilege.
For users with the correct privilege, use no_query_option.
This obviously requires you to check the user's privilege before
activating the desire form.
(2) In the pre-form trigger, check the user privilege. If he does not have the correct access,
issue the command:
set_block_property(block_name,UPDATE_ALLOWED,PROPERTY_FALSE);
[Quoted] Tracey Berukoff <"<tlberukoff>"_at_boco.co.gov> wrote in article
<344249CC.6C0C_at_boco.co.gov>...
> I am developing a reasonably simple app which requires two security
> levels. Some users can update, some can only view. The canvases will
> look exactly the same for both. Do I want to create 2 separate forms, 1
> updateable and 1 viewable, or can I create one form and change
> properties based on user roles? I'm sure there is one way that is much
> more logical but it's not coming to me on this Monday morning. I can't
> find any reference to security except through menus. Any help would be
> appreciated.
>
> Thanks, Tracey
>
Received on Mon Oct 13 1997 - 00:00:00 CEST