Originally Posted by JCapp
..They want as much as possible to be based on VBA code due to the size of the tool/database we're working with.
I can't follow that statement, why do they think a lot of VBA code should reduce the database size versus an already created report?
What really increases a database in size, is if images are stored direct in a MS-Access database, or if queries are run where many data are involved, that really bloat a MS-Access database, (therefore remember to do a Compact & Repair).
Remember a report is more a static view of data, (printed on paper), I you want something to expand/collapse then use a form.