Pulling Check Box's on form

[BartK]

Sorry meant to put putting instead of pulling

Here is my situation, I have a form that I want to bring up and then in that form have multiple multiple check box's that I can check and then based upon what I check I would like to be able to store that info in a separate table.

My problem is:
First I can't find the check box on the design view of my table and then is what I'm asking even possible without getting overly complicated?

I'm wanting to have the same information entered/stored in the table exactly over and over again.

Thanks all.

 

[Pat Hartman]

A checkbox is a visual representation of a yes/no data type. If you want to display a checkbox for another numeric data type, you need to use a form or report. You should always use forms and reports for presentation anyway. Raw tables and queries should NEVER, under any conditions, be presented to users.

 

[BartK]

Pat,
Agreed, I probably wasn't being all that clear earlier. Ultimately what I would like to do is to have the user hit a button which would take them to another form. On that form, I think I'm needing check boxes here, but I could be mistaken. There are going to be multiple fields that I would like to user to check/click and after they exit that form that data is saved in a new record that the user is currently working on.

I could post my DB and probably "mock" something up to help you get a better idea. Thanks again.

 

[David R]

A mockup we can look at (critique) sounds best. The line " I'm wanting to have the same information entered/stored in the table exactly over and over again." concerns me because it sounds like your data tables are not set up correctly for a relational database.

Have you learned about normalization yet? Access is not a spreadsheet.

 

[BartK]

I will attach my DB that I am currently working on, however please keep in mind that I have only been working on this for about the last day. As for having the same information input in exactly the same time and time again is a little crucial for what we are wanting the DB to do. It is going to be our Injury/Illness DB here at this company.

Please feel free to critique/change whatever you think would be a better way to go. This kind of got dumped in my lap the day before yesterday. Thanks once again for everything.