I checked your sample app.

To me, this is not "expected behavior" but it still happens. I think the only thing you can do is make the other columns also invisible depending on the value for confidential.

If this is a lot of work, if all covering labels are named the same way, or if they all have the same or similar condition for visibility, you might be able to do something in the constructor of the dw (or when changing the dataobject dynamically from code), check on "confidential in their visibility condition":

- loop through all text objects of the dw and check if there's one in the list for which the visibility condition holds the string "confidential", Get the x position and width of that one.

- for all other columns, check if their x position falls between the previously read "x and x + width" positions. If so, add their visibility condition using Modify().

HIH

Hi Dan,

If confidential means "user cannot see" then you could consider using function = dw . SetDetailHeight like this code:

// Event = ue_SetAccessLevel( long al_userAccessLevel )
// This script hides all rows requiring security clearance above <userAccessLevel>
long row

this.SetRedraw(false)
for row = this.RowCount() to 1 step -1
   if al_userAccessLevel < this.object.AdminSecurityLevel[row] then
      // Lack of access => Hide this row
      this.SetDetailHeight(row, row, 0)
   end if
next
this.SetRedraw(true)

NOTE: AutoSizeHeight will override any row height set by SetDetailHeight so watch out for "counterproductive" DataWindow configuration.

NOTE: A couple of performance tricks

• SetRedraw ensures only one screen paint despite potentially hiding hundreds of rows.
• Reverse loop from RowCount down to 1 ensures RowCount function is called just once. Same can be done incrementing but less efficient. Incrementing row requires either call RowCount to check after each iteration - or assign to extra local variable.

HTH /Michael