One ring (checkbox) to control them all

[jree3000]

I have a form which uses multiple checkboxes. I want one check box to be a "check all" (check the 12 other checkboxes whenever the "check all" becomes checked). Any ideas how I go about achieving this? Thanks in advance for your time.

[Bob Fitz]

Do you also want to "uncheck" the other 12 checkboxes when "check all" becomes unchecked.

[jree3000]

Yes. I think that would work best functionally.

[Bob Fitz]

Perhaps something like:

Private Sub Check1_AfterUpdate()  
  Me.Check2 = Me.ActiveControl
  Me.Check3 = Me.ActiveControl
  Me.Check4 = Me.ActiveControl
  Me.Check5 = Me.ActiveControl
'etc
End Sub

[June7]

Multiple checkboxes - I suspect non-normalized data structure.

[jree3000]

Perfect! Much obliged!

[Bob Fitz]

Multiple checkboxes - I suspect non-normalized data structure.

Yes, it would not be surprising.

[jree3000]

What makes you say that? I believe the data is normalized but admittedly I am far from an expert. All entered data is stored in tables, with no redundancy. The tables are linked as they should be. There are several queries that use the data in these tables to give me additional data. I have tested and verified that the data in my records is as it should be. What is wrong with that?

[June7]

I did say 'suspect' - would need to know more about the table structure to be sure. An example of multiple checkboxes that is not normalized data - table of pets owned by people:

OwnerID	Cat	Dog	Bird	Fish
1	x			x
2	x	x
3		x
4			x

Even if these were text with species info or number with quantity of pets, would not be normalized.

[jree3000]

I see. I'm not using them like that. I'm basically using them as a control to assist in calculating an inventory query. I have to keep track of all items processed but some items processed do not pass inspection, those items are discarded and therefore not entered into inventory. There are a dozen different sublevels to each inventory item, each must pass a test to be entered into inventory, if not they are discarded, but again I must track them regardless. It's a fairly complex process/system so it requires a bit of creativity in the way I track everything. I have been testing everything as I create though to make sure data is sound. Thanks!

[June7]

Does sound like an unusual db.

[ItsMe]

If a mechanic had one Work Order to work on one car, doing a 50 point inspection, it may be OK to use 50 Yes/No fields in a single table. But, what do you do when one of the inspection points fail? Do you just tell the customer that the mechanic did not like it or do you offer some "Detail" about why?

If there are sublevels to the status of an entity being prepared for inventory status, each sublevel may need its own table.

[jree3000]

Unusual db is an understatement. I have a NDA so I can't discuss specifics but think of it less like a car inspection and more like a cherry pie, cherry extraction process. Each pie is cut into 12 pieces tracked by relative position. Each piece has x number of cherries in it. Each piece is inspected for contamination. If a piece fails inspection, those cherries are not counted into cherry inventory. But it is still important to know how many cherries there were in the first place in each piece and the pie as a whole. Kind of a kooky analogy but it was the best I could do off the top of my head.

The checkboxes basically let me know if portions of these items can be added to the inventory query or not. So far it all tests out properly but I would definitely say this is an unusual db in both purpose and probably execution.

I do appreciate all of the help and input, gentlemen. Thanks again!