I think you misunderstand the DB
I didn't understand it at all, except that there were a large number of choices to be handled in some way.
The user will tick off any found from a list of 105 and those have to be inserted into the report
I assume you would be storing the information, so the choices would be stored in a table, then the report would be run. Or are the values being inserted into an unbound control on the report?
Assuming the information is being stored, I would expect there to be a table containing the deficiencies listing, another for the report record, and a junction table for the deficiencies that pertain to the report. It would have helped to know something about the basis for the report (is it a daily report of deficiencies, or the deficiencies for a manufacturing process, or what?). I will assume a daily report, although it doesn't really matter for purposes of the sample table structure:
Deficiency (text description of the deficiency)
ReportID (link to tblReport)
DeficiencyID (link to tblDeficiency)
For the interface, a form based on tblReport, with a subform (continuous) based on tblReportDeficiency. The Link Master and Link Child properties of the subform control (the "box" containing the subform) set to ReportID. On the subform, bound to DeficiencyID, a combo box. The combo box Row Source is a query based on tblDeficiencies. The combo box Column Count is 2, Column Widths something like 0";1.5", Bound Column 1. This will let you select as many deficiencies as needed.
For the report, you could use a report/subreport the same as for the form.