I have been unable to make individual radio buttons ReadOnly or Invisible.  I have come to believe that we cannot currently do that.

I can make the whole Radio Button Group change status, but not the individual buttons.

===========================

For example I have a Radio Group with 8 Status options.  When one option is selected, I would like to then limit the choices that can be selected based on that.  For example if a Job Order is Open, I do not want to be able to change Status to Deleted, but that choice might be OK if the order is not yet released to Production.

The only workaround I have right now is to make multiple Radio Groups that sit in the same position, and change the status of each of those based on value of the "active" Status group.  So if Status3 is selected, the RadioGroup 7 might be "active" (visible and not ReadOnly)  but all others are "inactive" (Invisible and ReadOnly).  But if Status 5 is selected, then RadioGroup2 might be active and the others inactive.

Would like to have an easier option to deal with this.  Is there a tool I have overlooked?  If not, perhaps this might be available in next release?

Thanks for listening.

Symptom happens when doing Test Program in Program Editor.  Error cursor appears beneath the element name.

Here is a shorter version, same issue:

Radio Group is named OrderType
Options are Purchase Order, Sales Order, Job Order

When PO is selected, then SO and JO should be ReadOnly and/or Invisible so user cannot change after selection.

The sample below is showing four lines that each fail.  Would not normally use all four like this, but just trying to show four line that each fail.

IF OrderType = "Purchase Order" THEN {
	ReadOnly(rbtnSalesOrder,1)
	ReadOnly(OrderType!rbtnSalesOrder,1)
	visibility(rbtnSalesOrder,0)
	visibility(OrderType!rbtnSalesOrder,0)
	} 

Code is set when Element Changes and when Form is Entered.  Various elements, labels, colors, etc.  are changed based on OrderType.  This allows selection when record is Added, but does not allow changing.  And it also provides proper visual presentation when record is opened in future.


======================
Subsequent Edit:     
Never mind.  Problem fixed.  Thanks for confirming that feature was available now.

Thanks for forcing me to provide code.  The dummy at this end was using the wrong names for the radio buttons in the coding.  Actual names were rbSalesOrder, etc. not rbtn.....
Carry over from changing my naming conventions. 

Aaaargh!