Creating report by adding data with checkboxes

[geospatial]

Trying to automate the creation of memorandums. In the memo i want to be able to create lists with individuals names and job title, but I want to be able to do it by check box.

For instance I will have a row that says. Primary User. Under Primary user it could have 1 individual or it could have 10 individuals. Once those are all listed there is a row that has alternate users and same it could be 1 individual or multiple.

What I would like is when the report opens to have a drop down or checkboxes of all individuals in my personnel table. For instance it could have a pop up that says add primary users and then shows all individuals in the table. I put checkboxes next to all those I want and then I hit a button to accept and it adds those. Then it ask for alternate and does the same thing. After that it opens the report with the data.

Another question would be is if this makes sense to do it this way or to have another table that puts additional duties in and then query from there? Any thoughts on how to get the final product would be appreciated.

 

[Micron]

What I would like is when the report opens to have a drop down or checkboxes of all individuals in my personnel table. For instance it could have a pop up that says add primary users and then shows all individuals in the table. I put checkboxes next to all those I want and then I hit a button to accept and it adds those.

No it doesn't make a lot of sense. Reports are not made to be interactive. If you want to be interactive with records, you need to do it on a form. If you also don't know whether or not you need another table, then I get the sense you don't understand db normalization or relational theory. If that is the case, you are pretty much doomed to spending a lot of time struggling with something that probably will never meet your expectations. Maybe check out as much of this as you can, then post back if you want to continue on your present path:
Normalization is paramount. Diagramming maybe not so much for some people.

Normalization Parts I, II, III, IV, and V
Roger's Access Blog: What Is Normalization, Part I
and/or
Database Normalization Full Tutorial

Entity-Relationship Diagramming: Part I, II, III and IV
Roger's Access Blog: Entity-Relationship Diagramming: Part I

How do I Create an Application in Microsoft Access?
Roger's Access Blog: How do I Create an Application in Microsoft Access?

Important for success:
One source about how to name things - http://access.mvps.org/access/general/gen0012.htm
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm

The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
About calculated table fields - http://allenbrowne.com/casu-14.html

 

[geospatial]

Thanks. I appreciate the condescending tone that since i asked a question I must not know anything. That really helps people try to continue on with what they are doing. I also understand normalization and rational theory, which my question has nothing to do with. The question on adding another table was to ask if it would make more sense to just have that extra table with the data in it and query from there. The original question does not have that information, and I didnt really want to store that information. I was hoping I could just choose certain individuals and mark them for a primary or alternate role specifically for that one report and then hit print. If that was to hard to do then I was going to create a table with the information.

 

[Micron]

I appreciate the condescending tone that since i asked a question I must not know anything.

Sorry you took it that way. You asked a direct question and I thought I was being helpful. Not my fault if I took your post to mean you needed such info, for which I take the effort to pass on to those I think could benefit from it.
Since you have an issue with my approach, from now on I will be sure to not trouble you with my style of help since it aggravates you so much.