Class to control multiple option buttons affecting differenet textboxes

Hello cpietka,

Welcome to the Forum!

I really need to see what code you have written so far. The best option is to post a copy of your workbook.

How To Post Your Workbook

1. At the bottom right of the Reply window, Click the button Go Advanced
2. At the top of the Your Message Window, in the first row of icons, Click the Paperclip icon.
3. Click the Add Files button at the top right in the dialog box. This displays the File Manager dialog.
4. Click the Select Files button at the bottom middle of the dialog.
5. In the new window Find the file you want to upload, select it, and Click Open.
6. You will now be back in the File Manager dialog. Click the bottom Middle button Upload File.
7. Wait until the file has completely uploaded before you exit the File Manager dialog.

Hello cpietka,

Thanks for posting the workbook.I only count 24 Option Buttons on the UserForm. I think you are counting by the assigned name index. You have deleted a few from this workbook.

Can you provide me with more details about these groups and which buttons should be in which group? Tell me which page they are on Disinfectant, Dechlorination, or Coagulant.

I think that this will help you.

In the attached, there is a class, clsLinkedControl.
A clsLinkedControl object has properties:
.BooleanControl - either a checkbox or an option button
.HideWhenFalse - a collection of controls. The Visible property of each of these controls will be set to False, whenever .BooleanControl is False
.HideWhenTrue - a collection of controls. Their .Visible will be false when .BooleanControl.Value = True
.ShowWhenFalse - a collection whose .Visible will be True when .BooleanControl.Value = False
.ShowWhenTrue - a collection whose .Visible will be True when .BooleanControl.Value = True

There are methods .AddHideWhenFalse, .AddHideWhenTrue, .AddShowWhenFalse, .AddShowWhenTrue that add controls to these collections

There is also a class to hold them, clsLinkedControls

clsLinkedControls has an .Add function. The first (required) argument of .Add is the .BooleanControl of the clsLinkedControl that is being added.

This code (in the Userform_Intialize) will show TextBox1 and TextBox2 when CheckBox1 is True and hide them when it is false. But TextBox3's visibility will be the inverse of CheckBox1. Textbox1 and TextBox2 are said to match CheckBox1, TextBox3 is said to invert CheckBox1

Please Login or Register  to view this content.

.Add will accept other (optional) arguments
.Add(BooleanControl, (optional)list of matching controls, (optional boolean) inverse flag, (optional) list of inverting controls)

The above code could be replaced by

Please Login or Register  to view this content.

All of your OptionButton and CheckBox event code has been replaced by this block in the Userform_Initilaize event

Please Login or Register  to view this content.

I've changed clsLinkedControl and clsLinkedControls to make it more versatile and more intuitive.

clsLinkedControl.BooleanControl can now be any control, not just an OptionButton or CheckBox.
BooleanControl is deemed to be True if its value equals the .TrueValue property of the clsLinkedControl object.
Although currently written for only CheckBoxes, OptionButtons and ComboBoxes, adding a new kind of control is pretty transparent.
There are two new properties, .ClearWhenTrue and .ClearWhenFalse. Both are collections of controls whose values will be set to vbNullString when the BooleanControl is True (or False). The methods .AddClearWhenFalse and .AddClearWhenTrue have also been added.
In addition, there are methods .FollowBooleanControl and .InvertBooleanControl. Passing a user form's control as an argument for these methods will cause the control's visibility to either follow or invert the value of the BooleanControl.

I've changed the confusing syntax for the clsLinkedControls .Add method.
It now requires a msforms.Control object for the BooleanControl
The second argument, TrueValue, is optional and defaults to True.

This will make is so TextBox1 and TextBox2 are visible if, and only if, OptionButton1 is checked. TextBox3 will be visible iif OptionButton1 is unchecked.

Please Login or Register  to view this content.

This will make it so TextBox5 is visible iff ComboBox1.Value = "cat". Also, whenever ComboBox1.Value is changed to "cat", TextBox7 will be cleared

Please Login or Register  to view this content.

Here is the code for the new clsLinkedControl

Please Login or Register  to view this content.

and the new clsLinkedControls

Please Login or Register  to view this content.

Now I need to go to the OP's workbook and alter the Initialize event. And include the ComboBoxes.

OK, I've incorporated this into the user form.

Your using the Intialize event as a reset routine required that I move the class set-up into the Activate event.
I also had issues with setting up clsLinkedControl objects for the ComboBoxes.

Initially, I planned to use one clsLinkedControl object per combo box

Please Login or Register  to view this content.

But clearing the combo box would trigger the BooleanControl_Change event. So I had to use two clsLinkedControl objects, with different .TrueValue's and only use the ...WhenTrue collections. Preserving the "If ComboBox1.Value = vbNullString Then do nothing"

Please Login or Register  to view this content.

Here's the whole Active Event.

Please Login or Register  to view this content.

I think this version of the custom classes is more intuitive and easier to edit.

I'm taking another look at your situation.
Rather than focusing on code for every OptionButton, what I'm seeing is that you have frames.
Some frames enclose one text box.
Others enclose two textboxes and an option button pair that toggles one of the textboxes between user entered value and a default.
Others enclose four textboxes and an option button pair.

These three kinds of frames, and their controls, could be cast as custom Controls.

Similarly you have two kinds of choosers. One kind is an option button pair, the other kind is a combobox. That's two more custom Controls.

These custom Controls can be grouped together One controller decides which of the custom multi-textboxs to show. Those groupings can be made into other custom controls.

I need some time to develop this, but I hope the result is more transparent than the global "control every option button" style I used above.

I looked at your reduced user form in post #10.
Could I suggest a slightly different interface rather than two option buttons.

Two option buttons working together are functionally the same as a check box. Either one of the buttons is on or the other. Either the CheckBox is clicked or its not.
Two option buttons = One check box.

So I'd suggest using one CheckBox with one TextBox. (The .Caption of the CheckBox could be "Use previous from yesterday")

I'd also suggest that you calculate all of these yesterday values in the initialize event and put them in the respective .Tag properties of the TextBox (or the CheckBox)

That would reduce the code for each entry to

Please Login or Register  to view this content.

Note that, after the .Tag was set to yesterday's value in the Initialize event, you don't have to test anything when reading the "Previous" value. Its whatever is in TextBox1.Text

The machinery of setting up a custom class to do this and assigning each check box to its text box is not worth the effort IMO.

I'll be working on componentizing the OP user form so you can add tanks easily.

Its been a while, but I have been wrestling with the Creeping Feature Creature on this one.

In the attached, a clsDefaultButton object is a TextBox and a Controller.
The Controller is either a CheckBox, an OptionButton or a ToggleButton.
When the Controller is checked, the TextBox is filled with the .DefaultValue, when not, the TextBox will accept user entry from the keyboard.

A clsDefaultBox is instansized with code like

Please Login or Register  to view this content.

When CheckBox1 is clicked (so that Controller.Value = DefaultBox1.UseDefaultWhen) the .DefaultValue (today's date) is put in TextBox1.

clsDefaultBox objects have a Change event.
DefaultBox1.Reset will reset the Controller and TextBox to the .ResetControllerValue and the .ResetTextBoxValue

These are the properties of a clsDefaultBox

Please Login or Register  to view this content.

In the attached, Userform1 there is a multi-page.
On page 1, there is a CheckBox style clsDefaultBox, DefaultBox1, and a Reset button, which resets DefaultBox1
The DefaultBox1_Change event puts the DefaultBox1.Value into a Label.

There is also a Monitor that allows you to change the properties of that clsDefaultBox (similar to the Properties window in the VBEditor)

Page2 has an OptionButton style clsDefaultBox and Page3 has a ToggleButton style.

Userform2 goes with Sheet2 and is an implementation from post #6(?)

As I've said, I've been struggling with the Creeping Feature Creature.
Features that one might add:
-Validation, the clsDefaultBox might restrict user entry to numeric or integer entry from the keyboard.

-.UnDefaultTextValue - as written when the Controller is changed from UseDefaultWhen, the default value remains in the TextBox (the user can edit it). One could code a .UnDefaultTextValue property that specified some other string to fill the TextBox in that situation.

- a ToggleButton style clsDefaultBox could be made to toggle the ToggleButton's .Caption between the clsDefault object's .Caption and .Caption2 properties.