Check box in access

[rad]

I am stuck with this problem. I need to create form with checkbox that
must be populated dynamically from a table. For example, if I have a
table called Fruits, and the values are "Apple", "Orange", "grapes", I
need a form with 3 check box (should be able to view all in the same
screen). If i add one more fruit, then the form must automatically
change to reflect this. How would I go about doing this?
Thanks
Rad

[(PeteCresswell)]

Per rad:

I am stuck with this problem. I need to create form with checkbox that
must be populated dynamically from a table. For example, if I have a
table called Fruits, and the values are "Apple", "Orange", "grapes", I
need a form with 3 check box (should be able to view all in the same
screen). If i add one more fruit, then the form must automatically
change to reflect this. How would I go about doing this?

How about a little more detail on what's underneath.

So far, it's sounding like a combo box or radio button group.

Not checkboxes because the property values are mutually-exclusive. i.e.
something cannot both Apple and Orange.
--
PeteCresswell

[Bob Quintal]

"rad" <rv******@vt.edu> wrote in
news:11*********************@p10g2000cwp.googlegro ups.com:

I am stuck with this problem. I need to create form with
checkbox that must be populated dynamically from a table. For
example, if I have a table called Fruits, and the values are
"Apple", "Orange", "grapes", I need a form with 3 check box
(should be able to view all in the same screen). If i add one
more fruit, then the form must automatically change to reflect
this. How would I go about doing this?
Thanks
Rad

There are several approaches to this, none of which work. ;^)
One way is to use a subform disguised to look like a row of
labels and checkboxes.

Another is to put a bunch of hidden labels and checkboxes and
use code to scan the fruits table, add the fruit name to the
label and unhide the label and checkbox each time you open the
form.

Both these have the advantage of removing the box when the value
is removed from the fruit table.

The issue has to do with the purpose of the checkbox, whether
it's to store true or false in a table, to control a filter in a
report, etc.

These are not fun things to code. Better you use a multiselect
listbox.
--
Bob Quintal

PA is y I've altered my email address.

[(PeteCresswell)]

Per (PeteCresswell):

So far, it's sounding like a combo box or radio button group.

And, of course, a combo box would eliminate the issue of adapting
to added values in the range.

In the table you store something like FruitTypeID.

Then you have a lookup table like tlkpFruitType:

FruitTypID FruitTypeName
--------- -------------
1 Apples
2 Oranges
3 Pears
The combo box's .ControlSource=FruitTypeID in the main table.

The combo box's .RowSource = tlkpFruitType.
--
PeteCresswell

[radhika.vedaraman]

A combo box sounds like a good idea, but may not fit what I have in
mind.

I have 2 tables. One is the fruits table that Peter listed

FruitTypID FruitTypeName
--------- -------------
1 Apples
2 Oranges
3 Pears
Another is the list of users and the fruits of their choice.
User FruitTypID
------- ----------------
Rad 1
Peter 1
Peter 2
Now, I need a form that would have one user at a time, and list all the
available fruits, and have only the fruits of choice, checked.

ie. The form for Rad will have 3 check boxes,: Apple, Orange, Pear. But
only Apple will be checked.
For Peter, both Apple and Orange will be checked. This form must
provide the capability to alter the fruits of my choice. So Rad can
uncheck Apple and select pear and orange instead, etc.

Hope I am making sense!!

Thanks a lot
Rad

[(PeteCresswell)]

Per ra***************@gmail.com:

Now, I need a form that would have one user at a time, and list all the
available fruits, and have only the fruits of choice, checked.

ie. The form for Rad will have 3 check boxes,: Apple, Orange, Pear. But
only Apple will be checked.
For Peter, both Apple and Orange will be checked. This form must
provide the capability to alter the fruits of my choice. So Rad can
uncheck Apple and select pear and orange instead, etc.

You need a third "link" table between tblUser and tblFruit.

tblUser ==> tblUserFruit ==> tlkpFruit.

tblUser:
---------
UserName
UserNumber (just an AutoNumber PK)
tblUserFruit:
--------------
UserNumber
FruitID
tlkpFruit:
-------------
FruitID
FruitName
If JoeUser (whose UserNumber is 14) likes apples and pears, tblUserFruit will
have two records in it for him:

14 01
14 03
frmUser will have a subform on it: frmUserFruit, whose .RecordSource
is tblUserFruit and whose subform linkage specify UserNumber. Either that or
..RecordSource = a query with a criteria of UserNumber=frmUser.txtUserNumber.
--
PeteCresswell

[radhika.vedaraman]

Great! I think this will work for me! Appreciate your help, Peter