Checkboxes in Continuous Forms View All Linked

[nickh]

I have been using Access for about a year, but only doing basic relational databases and queries. Now I would like to start expanding my skills to include more functional forms and reports. My first attempt at forms is to create a sign in sheet for an organization's events. I would like to use a table of members to populate a form where the person checking in each member could simply check the checkbox in front of each member's name and have Access automatically add a record in an event_attendance table.



My research so far showed me that I can create the form with all the members listed by changing the form's Default View property to "Continuous Forms". I then can add a checkbox in front of each member's name and view it in "Form View" without any issues. However, checking the checkbox in front of any member's name results in the checkboxes in front of every member's name being checked as well. Is there a way to decouple the checkboxes in a Continuous Form?

After that I'll have to find a way to create a record using that member's information and some information about the event. I assume that will involve adding some VB code to the checkbox's Event > On Click property unless someone knows of an easier way to achieve the same results.

[RuralGuy]

In order to not have the checkbox in front of everyone's name in a continuous form you would need to Bind that checkbox to a field in the recordsource of the form, which means you would probably need to add a field to that table. You might consider a Command Button instead that would add a record to the event_attendance table. You could add a Message Box to the code to make sure they intended to press the button.

[ItsMe]

Edit: Hah, I took too long to type.

A continuous form is simply a little magic trick that displays all of the records within a recordset at one time. If you open a form in Form View, you will see one record within the recordset. While in form view, you can navigate to the next record, or the last record, or the precious record, etc. All the while, only one of the records within the set is active or Current.

A similar thing happens with the Continuous form. When you click on a record within Continuous View, that record has the focus and, therefore, that record is the Current Record. The Controls are just there to represent a field. The magic is that the controls are, really, one control repeated many times.

In your case, you are using an unbound control. It is not associated with a field. When you select a record within the set, the control is not associated with the current record. It is associated with nothing. It is unbound.

Maybe you can add a column to your table that would indicate if a specific record is earmarked for Attending or AttendHold or ...

[RuralGuy]

@ItsMe: It is because the air is thinner up here!

[nickh]

Thanks RuralGuy. That fixed the issue with the checkboxes being linked together. I just created a Yes/No field in the membership table which allowed me to bind the checkbox to something that wouldn't corrupt my data.

I had thought about using a button, but thought it would be more intuitive if the person checking in people viewed it as a check list. Having a button that looked the same after it was clicked could leave the person checking in the member uncertain if they had actually recorded that person's name. Essentially the checkbox provides a positive indication some action was actually performed for that member that I don't think a button would provide.

[RuralGuy]

You're very welcome. Glad we could help.

[CJ_London]

this is an alternative - doesn't use checkboxes, but also doesn't require a yes/no field in the table.

https://www.accessforums.net/showthr...773#post330773