Hi all,

I have a requirement to implement a master-detail sheet. That's ok.
However, based on the user-logged-in credential, the user may OR may
not be able to edit the details part.

Now I can easily implement this by adding a constraint while updating
the details' data.

if user_can_edit then
    update
end if

The problem is this:
If the user is not entitled to make changes, he is still able to put
focus to the details' form data and modify (of course I am not
updating it)...but the user can get a feeling "oh I am able to modify
the data".

Is it somehow possible to make the details' textboxes/single-line-
edits editable IF user is entitled to make changes? OTHERWISE, the
details' textboxes/single-line-edits will be made UNEDITABLE.

Thanks in advance,
@maram

The simplest way would be <DW Control 
Name>.Modify("DataWindow.ReadOnly=Yes")

"achuta" <atmaram.mulliah@gmail.com> wrote in message 
news:dd824f33-e313-4228-8a63-b0294b54ca7b@z27g2000prd.googlegroups.com...
> Hi all,
>
> I have a requirement to implement a master-detail sheet. That's ok.
> However, based on the user-logged-in credential, the user may OR may
> not be able to edit the details part.
>
> Now I can easily implement this by adding a constraint while updating
> the details' data.
>
> if user_can_edit then
>    update
> end if
>
> The problem is this:
> If the user is not entitled to make changes, he is still able to put
> focus to the details' form data and modify (of course I am not
> updating it)...but the user can get a feeling "oh I am able to modify
> the data".
>
> Is it somehow possible to make the details' textboxes/single-line-
> edits editable IF user is entitled to make changes? OTHERWISE, the
> details' textboxes/single-line-edits will be made UNEDITABLE.
>
> Thanks in advance,
> @maram 

Couple that, or course, with the Enabled property for non-DataWindow 
controls. When you open the window, check the user's credentials and 
change these properties as appropriate.

The PFC has a very robust security module that can make all of this much 
easier. At one time, I had acquired a version of that module that had 
been extracted from the PFC. Though I don't have that code any more, I 
know it's possible to do.



Jerry Siegel [TeamSybase] wrote:
> The simplest way would be <DW Control 
> Name>.Modify("DataWindow.ReadOnly=Yes")
> 
> "achuta" <atmaram.mulliah@gmail.com> wrote in message 
> news:dd824f33-e313-4228-8a63-b0294b54ca7b@z27g2000prd.googlegroups.com...
>> Hi all,
>>
>> I have a requirement to implement a master-detail sheet. That's ok.
>> However, based on the user-logged-in credential, the user may OR may
>> not be able to edit the details part.
>>
>> Now I can easily implement this by adding a constraint while updating
>> the details' data.
>>
>> if user_can_edit then
>>    update
>> end if
>>
>> The problem is this:
>> If the user is not entitled to make changes, he is still able to put
>> focus to the details' form data and modify (of course I am not
>> updating it)...but the user can get a feeling "oh I am able to modify
>> the data".
>>
>> Is it somehow possible to make the details' textboxes/single-line-
>> edits editable IF user is entitled to make changes? OTHERWISE, the
>> details' textboxes/single-line-edits will be made UNEDITABLE.
>>
>> Thanks in advance,
>> @maram 
> 
> 

PowerTOOL, a framework that was very popular before the PFC was created, 
also had security built in. I added a column to the user/window table for 
read-only, then put all the logic to massage the datawindow into an NVO. [I 
don't work there anymore and the code was proprietary anyway, don't ask]

"Jason 'Bug' Fenter [TeamSybase]" 
<NO_SPAMMING_jason.fenter_@_teamsybase.com> wrote in message 
news:49788faf$1@forums-1-dub...
> Couple that, or course, with the Enabled property for non-DataWindow 
> controls. When you open the window, check the user's credentials and 
> change these properties as appropriate.
>
> The PFC has a very robust security module that can make all of this much 
> easier. At one time, I had acquired a version of that module that had been 
> extracted from the PFC. Though I don't have that code any more, I know 
> it's possible to do.
>
>
>
> Jerry Siegel [TeamSybase] wrote:
>> The simplest way would be <DW Control 
>> Name>.Modify("DataWindow.ReadOnly=Yes")
>>
>> "achuta" <atmaram.mulliah@gmail.com> wrote in message 
>> news:dd824f33-e313-4228-8a63-b0294b54ca7b@z27g2000prd.googlegroups.com...
>>> Hi all,
>>>
>>> I have a requirement to implement a master-detail sheet. That's ok.
>>> However, based on the user-logged-in credential, the user may OR may
>>> not be able to edit the details part.
>>>
>>> Now I can easily implement this by adding a constraint while updating
>>> the details' data.
>>>
>>> if user_can_edit then
>>>    update
>>> end if
>>>
>>> The problem is this:
>>> If the user is not entitled to make changes, he is still able to put
>>> focus to the details' form data and modify (of course I am not
>>> updating it)...but the user can get a feeling "oh I am able to modify
>>> the data".
>>>
>>> Is it somehow possible to make the details' textboxes/single-line-
>>> edits editable IF user is entitled to make changes? OTHERWISE, the
>>> details' textboxes/single-line-edits will be made UNEDITABLE.
>>>
>>> Thanks in advance,
>>> @maram
>> 

The simple (not best) way....
Have two detail datawindows.  Load the non-editable one when
the window opnes, if the user cannot edit.

(You could also set the properties of each field in the
ue_postopen event, if you don't like the two-datawindow
solution.)

HTH KL
> PowerTOOL, a framework that was very popular before the
> PFC was created,  also had security built in. I added a
> column to the user/window table for  read-only, then put
> all the logic to massage the datawindow into an NVO. [I
> don't work there anymore and the code was proprietary
> anyway, don't ask]
>
> "Jason 'Bug' Fenter [TeamSybase]"
> <NO_SPAMMING_jason.fenter_@_teamsybase.com> wrote in
> message  news:49788faf$1@forums-1-dub...
> > Couple that, or course, with the Enabled property for
> > non-DataWindow  controls. When you open the window,
> > check the user's credentials and  change these
> properties as appropriate. >
> > The PFC has a very robust security module that can make
> > all of this much  easier. At one time, I had acquired a
> > version of that module that had been  extracted from the
> > PFC. Though I don't have that code any more, I know
> it's possible to do. >
> >
> >
> > Jerry Siegel [TeamSybase] wrote:
> >> The simplest way would be <DW Control
> >> Name>.Modify("DataWindow.ReadOnly=Yes")
> >>
> >> "achuta" <atmaram.mulliah@gmail.com> wrote in message
> >>
> news:dd824f33-e313-4228-8a63-b0294b54ca7b@z27g2000prd.goog
> legroups.com... >>> Hi all,
> >>>
> >>> I have a requirement to implement a master-detail
> sheet. That's ok. >>> However, based on the user-logged-in
> credential, the user may OR may >>> not be able to edit
> the details part. >>>
> >>> Now I can easily implement this by adding a constraint
> while updating >>> the details' data.
> >>>
> >>> if user_can_edit then
> >>>    update
> >>> end if
> >>>
> >>> The problem is this:
> >>> If the user is not entitled to make changes, he is
> still able to put >>> focus to the details' form data and
> modify (of course I am not >>> updating it)...but the user
> can get a feeling "oh I am able to modify >>> the data".
> >>>
> >>> Is it somehow possible to make the details'
> textboxes/single-line- >>> edits editable IF user is
> entitled to make changes? OTHERWISE, the >>> details'
> textboxes/single-line-edits will be made UNEDITABLE. >>>
> >>> Thanks in advance,
> >>> @maram
> >>
>