I've had issues with VBA not running in Sub-Reports.  I'm really hoping someone can address this as it will help me out as well.

-Raymond

Watching

Some events are disabled in a subreport, such as the Detail Format event that runs every time a record is processed.  A subreport's Load event does not run, but the Open event does.  Mouse-related events do run in a subreport.  But crucially, the Detail events do not run in subreports.  The reason for all this is, I think, that a subreport is treated as a control, not a report per se.  (Confusingly, a subform *is* treated as a form, so all its VBA events work as usual.)

This is why I've never used subreports in reports.  When I create a report, I make sure all the data needed for the report are specified in the main report's record source, so I don't need a subreport to bring in additional data.

I ended up making unbound controls then using VBA to set values. After that I used the tag and sub in form load to set the control properties.  Works great.  I would have liked to make a sub report and get rid of all the extra controls. Oh Well.

Yeah, subreports can be a beast. I avoid them. That's why, for example, I teach using a big query with all the joined data from OrderT and OrderDetailT when making an invoice instead of using a subreport. I'd rather use grouping levels in the report.

The only time I ever use subreports is if I want to bring together completely different types of data. For example, I want to show a customer as the parent report, and then one subreport might show all of his contacts, a second subreport might show all of his orders. A third subreport might show all of the service technicians that have worked on his account. That kind of thing. Those three items, even though they're related to the customer, they're not things you can just bring together easily in a big query.