Hi Tracy;

 Personally, I think that the ReadOnly property is the best way "on the fly" but at design time, you can also set all the Tabs to Zero.  ;-)

Regards ... Chris 

Hi, Tracy - 

What we do in similar situations in our PFC application is is add a column in the DW's SELECT statement that does not map to any table/column and give it a name such as "protect_ind" ("ind" for "indicator") - and assign it a value in the SELECT statement (zero) that the Protect property of a column object can utilize and thereby protect the column from modification.

In each column's Protect property, we use a trivial expression like "protect_ind" with no If statement.

When conditions are such that the data values in a row need to be protected, the only thing the application has to do is set the value of the "protect_ind" column to 1, and voila, all of the column objects in that row are immediately protected.

Maybe you can use or adapt this technique for your purpose.

Best regards, John

dw.enabled = false

Might do what you need with a little less coding. :)

If your dw has columns with Edit, InkEdit or RichTextEdit type, they support column.DisplayOnly attribute. You can set the column background color to indicate editability and at runtime can select the column contents and copy them but cannot edit the data. If would be great if this attribute is supported for other widget types such as EditMask, DDDW, DDLB, RadioButton, Checkbox, etc. consistently.

dw.ReadOnly is better in conjunction with of_SetUpdateable( FALSE ) to protect all columns and data but still have interactivity.

You can use RMB menu options to be able to copy column content, copy all rows, etc.