Checkbox on Forms

[jdub via AccessMonster.com]

I created a form that lists all the players from a particular squad in my
database. I used the Wizard to create the form and populate the form with
the results from a sqad query. It works. My next phase is to add check
boxes to the form to allow the user to select the appropriate players that
will play in the next game and send the selected players to a form for
printing. I'm facing two issues. The first is that when I added the
checkbox to the form, each player returned in the form has a checkbox, which
is good. But when I select one checkbox it enables all of the checkboxes.
The second issue is how to I get the selected players to a report that will
list them in a column under Player Name? Any help would be greatly
appreciated.

Thanks

JW

--
<link removed>

[fredg]

On Tue, 06 Jun 2006 14:50:04 GMT, jdub via AccessMonster.c om wrote:

I created a form that lists all the players from a particular squad in my
database. I used the Wizard to create the form and populate the form with
the results from a sqad query. It works. My next phase is to add check
boxes to the form to allow the user to select the appropriate players that
will play in the next game and send the selected players to a form for
printing. I'm facing two issues. The first is that when I added the
checkbox to the form, each player returned in the form has a checkbox, which
is good. But when I select one checkbox it enables all of the checkboxes.
The second issue is how to I get the selected players to a report that will
list them in a column under Player Name? Any help would be greatly
appreciated.

Thanks

JW

You first need to add a check box field to the underlying table.
Then add that check box field to your form.
--
Fred
Please respond only to this newsgroup.
I do not reply to personal e-mail

[Rick Wannall]

Ifyou checkbox is not bound to a data field, then setting one sets all
instances.

First, you have to have a true/false field you can bind to for each player.

Second, you probably don't want that in your main data table, which I assume
you're using to populate your form. If the setting is temporary (you're
going to set it, use it a bit, and then you don't care) you can probably get
away with it in the main table. Doubtful. I'd probably make a table to
hold a list of player primary keys and a true/false field. With one action
query you can copy all the player primary key values to the foreign key
field in the new table, and also set the yes/no field to yes, or no,
whichever you prefer for the default.

then, your display, would be driven by the new table, and you could bind
your checkbox to the yes/no field.

And...you'll probably want to create more than one list eventually, so you
might as well create some ListID value and put that in the new table also.
You can either create it on the fly as you append the rows, or you can get
formal and have a ListMaster and ListDetail table pair. When you create a
new list, you put one row in ListMaster, get its primary key, and use that
primary key as a foriegn key in the new rows in ListDetail.

How elaborate do you want to be?

[jdub via AccessMonster.com]

Rick,

Thanks. I'm a newbie and think I follow your suggestions. I'm going to give
the a shot.

Jdub

Rick Wannall wrote:

Ifyou checkbox is not bound to a data field, then setting one sets all
instances.

First, you have to have a true/false field you can bind to for each player.

Second, you probably don't want that in your main data table, which I assume
you're using to populate your form. If the setting is temporary (you're
going to set it, use it a bit, and then you don't care) you can probably get
away with it in the main table. Doubtful. I'd probably make a table to
hold a list of player primary keys and a true/false field. With one action
query you can copy all the player primary key values to the foreign key
field in the new table, and also set the yes/no field to yes, or no,
whichever you prefer for the default.

then, your display, would be driven by the new table, and you could bind
your checkbox to the yes/no field.

And...you'll probably want to create more than one list eventually, so you
might as well create some ListID value and put that in the new table also.
You can either create it on the fly as you append the rows, or you can get
formal and have a ListMaster and ListDetail table pair. When you create a
new list, you put one row in ListMaster, get its primary key, and use that
primary key as a foriegn key in the new rows in ListDetail.

How elaborate do you want to be?

--
Message posted via http://www.accessmonster.com

[jdub via AccessMonster.com]

Fredg,

Thanks for your reply. Once I added the check box field to the table, how do
I get the results to a report?

Can the selections be Control Sources of some sort for the Player Name field
on the report?

Thanks,

JDUB

fredg wrote:

I created a form that lists all the players from a particular squad in my
database. I used the Wizard to create the form and populate the form with

[quoted text clipped - 11 lines]

JW

You first need to add a check box field to the underlying table.
Then add that check box field to your form.

--
Message posted via http://www.accessmonster.com

[Rick Wannall]

Typically:

docmd.openrepor t "MyReport", , , "MyYesNoField=T rue"

You may have additional criteria, of course, such as

docmd.openrepor t "MyReport", , , "MyYesNoField=T rue And ListID = '" &
Me.cboMyListID & "'"

[jdub via AccessMonster.com]

Rick,

I think I have thoroughly confused myself on this one. Steps I followed.

1. Created a field in the main database called Active Roster.
2. The Active Roster field has a datatype of Text
3. Added a Check box to the Roster Form
4. Without an empty Control Source Field, when the report runs, 1 click
selects all
5. When I enter the main database and field name in the control source field
and run the report, I'm unable to select any of them.

Help!!!!!

1. Should I make the data type for the roster field to be YES/NO?
2. What do I do with the checkbox?

Thanks,

JDUB

Rick Wannall wrote:

Ifyou checkbox is not bound to a data field, then setting one sets all
instances.

First, you have to have a true/false field you can bind to for each player.

Second, you probably don't want that in your main data table, which I assume
you're using to populate your form. If the setting is temporary (you're
going to set it, use it a bit, and then you don't care) you can probably get
away with it in the main table. Doubtful. I'd probably make a table to
hold a list of player primary keys and a true/false field. With one action
query you can copy all the player primary key values to the foreign key
field in the new table, and also set the yes/no field to yes, or no,
whichever you prefer for the default.

then, your display, would be driven by the new table, and you could bind
your checkbox to the yes/no field.

And...you'll probably want to create more than one list eventually, so you
might as well create some ListID value and put that in the new table also.
You can either create it on the fly as you append the rows, or you can get
formal and have a ListMaster and ListDetail table pair. When you create a
new list, you put one row in ListMaster, get its primary key, and use that
primary key as a foriegn key in the new rows in ListDetail.

How elaborate do you want to be?

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200606/1

[w_a_n_n_a_l_l_ -]

Are you truly entering the "main database and field name in the control
source field"? Controls in access bind to fields in tables and queries.

In the simple case, you'd have

tableName
NameID
ContactName
InRoster (this is the yes/no field)

On some subform in continuous form view, you'd put a checkbox in the detail
section, such as chkInRoster, bound to control source InRoster. The form
itself would be bound to the table tableName.

That's a bare-bones desription of a way to do what you're after, I think.

Then, once you check the boxes on theappropriate rows, you run your report:

docmd.openrepor t "MyRoster", ,,,"InRoster=Tr ue"

[jdub via AccessMonster.com]

Thanks for your help.

I'm good all the way up to the actual report. Where does this code go?

I've created a report that should list the selected player names in sequence.

I created a text box under the player name heading. Do I configure the
control source for this field???

What are the steps to put the selected records into the field?

Thanks,

Jdub

w_a_n_n_a_l_l_ -@-_s_b_c_g_l_o_b_ a_l._n_e_t wrote:

Are you truly entering the "main database and field name in the control
source field"? Controls in access bind to fields in tables and queries.

In the simple case, you'd have

tableName
NameID
ContactName
InRoster (this is the yes/no field)

On some subform in continuous form view, you'd put a checkbox in the detail
section, such as chkInRoster, bound to control source InRoster. The form
itself would be bound to the table tableName.

That's a bare-bones desription of a way to do what you're after, I think.

Then, once you check the boxes on theappropriate rows, you run your report:

docmd.openrepo rt "MyRoster", ,,,"InRoster=Tr ue"

--
Message posted via AccessMonster.c om
http://www.accessmonster.com/Uwe/For...ccess/200606/1

[w_a_n_n_a_l_l_ -]

If you're asking me about creating a report the best way is to select your
table in the database window and then click Insert | Report and choose
report wizard. Follow the prompts. Make a report. If you don't like how
it looks, delete it, do it again. The wizard is pretty simple. By the way,
tip: You don't have to display a field to filter by it. In other worods,
this statement:

docmd.openrepor t "MyRoster", , , "InRoster=T rue"

works whether InRoster appears on the report as a checkbox (or anything
else) or not. As long as the recordsource of the report is the table
itself, you have all the fields in that table available to you. You display
the players' names on the report by putting a control on the report and
using the player name field as the controlsource.