Fluffy, there are checkboxes and option buttons. These are sometimes placed
in a box called an option group. Only one option can be selected - when you
click on one, it turns off any other that happens to be on. Option buttons
have a dot that clicks on or off, while check boxes have a check that show
up when you click them.
In any case, if the buttons are placed in an option group, only ONE button
is allowed to be selected at a time.
Buttons NOT in an option group have no effect on each other. You can select
as many as you wish.
The general convention is to put option buttons in an option group. If you
need independent multiple selections, use check boxes, with no option group.
If you want the check boxes in a box for aesthetic reasons, use a rectangle
control.
HTH, UpRider
"Fluffy" <(E-Mail Removed)> wrote in message
news:FE459A69-664D-4825-9807-(E-Mail Removed)...
> "If you want to automatically populate some fields with fixed values when
> a
> particular checkbbox is checked, that's another matter, but not so
> difficult." That's exactly what I want to do. I think I may have done
> after
> I posted this afternoon. I ended up creating an option group w/11 check
> boxes. Values were assigned (by default, I think) & show up in the table.
>
> However, this option group allows me to only check 1 box. There are times
> when I need to check more than 1 box. What to do then?
>
> Sorry for the confusion -- I'm practically a newbie w/Access, but I enjoy
> learning.
> "UpRider" wrote:
>
>> Fluffy, your request is unclear. Are you actually having trouble placing
>> 12
>> checkboxes on the form, or are you having trouble getting the 12
>> checkboxes
>> to do what you want them to do?
>> If you store the value of the checkboxes in your table, the value will be
>> simply TRUE or FALSE. If you want to automatically populate some fields
>> with fixed values when a particular checkbbox is checked, that's another
>> matter, but not so difficult.
>> An event procedure for a checkbox could be so:
>> Private Sub chkInclude1_AfterUpdate()
>> Select Case chkInclude1
>> Case True
>> Call fcnShowSQL("SQL14a") ' or whatever
>> Call fcnFromYrReq ' or whatever
>> Call subCurrMOYR(0) ' etc
>> Case False
>> Call fcnShowSQL("SQL14") ' or whatever
>> Call fcnNoDatesReq ' etc
>> End Select
>>
>> As you can see, a multitude of actions can be taken for either true or
>> false. In your case true, you could move literals into textboxes bound to
>> your table, case false, equate those textboxes to NULL.
>>
>> UpRider
>>
>> "Fluffy" <(E-Mail Removed)> wrote in message
>> news:18D3A8EA-A06D-4C4E-865D-(E-Mail Removed)...
>> > I'm having a terrible time trying to insert 12 check boxes on a form.
>> > I'm
>> > setting up a rather small database to capture event info (name, date,
>> > location, type, etc). Since I plan to enter the info on the form, I'd
>> > like
>> > to be able to check as many boxes as applicable to the type of event &
>> > then
>> > have these items automatically carried over to the table. I haven't
>> > even
>> > started creating any reports yet; although one of the reports I will
>> > want
>> > will be broken by type of event. Can anyone offer me some simple
>> > solutions
>> > to adding some check boxes to my form?
>>
>>
>>
|
Similar Threads
