Select records to display in report.

[JefferyCT]

Ive been struggling with this for sometime, and no matter how many times ive tried to google it, i just cant seem to find my answer. Its probably glaringly obvious.

My question is: How do I use an unbound checkbox, in a sub-form, to select specific records and then generate a report that references those specific ones i selected?

Eg: the form/subform:

Name	Number	Selected
John Smith	+27 234189347	X
Peter Paul	+27 879872319
Mark Luke	+27 8977541631	x

The user then selects the records they want, then follow through to a report which shows only John and Mark' numbers, not Peter's

Ive tried:
1. adding a "selected" yes/no in the underlying tables, but this is not feasible do to table size, maintenance, etc.
2. Adding an unbound checkbox in a continuous form/table - thick changes all occurrences of the checkbox to the same value


3. Considered adding a custom field in a query, but not sure how i would do that without prompting for user input every time the underlying form is shown

I know there is an answer out there, i just cant seem to think of it myself. Any help or suggestions are welcome.

Thanks in advance,

(For traffic reasons it may be important to note that my Access FrontEnd runs of a mysql database online.)

[aytee111]

Have a button on each line, when user clicks on button write PK to temp table.

[JefferyCT]

That's a good answer, the temp table will be local, so no server traffic. That's awesome. I'm still going to leave the thread open to see if there are other ideas, but I'll try yours and let you know. Thanks a million!

[aytee111]

If there aren't too many records in the list, you could make it a listbox which allows multi-selection. This gets cumbersome with a large record count, tho.

[Gicu]

I usually run a make table query (or delete/append) to push in a local table all the PK (you can run it from the loading event of your reporting form); that table also has the yes/no field you need [Selected]. You then use that table in the record source of your selector form. This way you can have your users have independent selections. With this approach you will get some network traffic (when getting all the PKs) but because you only add the indexed PKs the query(s) should be fast.