> The desire is to manipulate them as a group - that > is, either they are all > visible or they are not visible. Would using the > same component ID, so as > to issue one PROPERTY command to change all of the > objects at once, cause > RBG7 troubles?
At present, I beleive it finds them all. However, unless RBTI states that this is a safe technique I wouldn't do this as future optimizations might break your code (for instance, they might want to quit after they find the first matching component). The traditional way to do this is to put your components in a group box or, if you don't want it apparent, a borderless panel, and then make the panel visible or invisible. If the components are spread around the form and not contiguous, then you can centralize the ON/OFF code in a Custom Form Action. Some of my forms have an action called SetUI which examines all the necessary variables and sets components to be enabled/visible, etc accordingly. -- Larry
