Access 2010 Report as Source Object in Access Form

Alison,

Although I cannot recall ever putting a report into a subform control, I'm guessing that when you do, Access uses the ReportView as opposed to the PrintPreview, and a lot of the events in the report don't fire properly in ReportView.

Have you tried manipulating the report behavior from within the main form?

>The SourceObject of the subform control is a report.
Even if this is possible, I highly recommend against it, as the properties of a report are different than a form.   For starters, reports are optimized to be printed on paper and with no user interface abilities, so none of the UI capabilities will work here.

Better to create a separate for to act as the subform.

I have never had a problem displaying a report in a form. It is a great way for a user to get a quick preview of how their data with be represented in the output. As an example you could have a preview of an invoice showing how the data entry will impact the printed invoice.

Also, manipulating the report behavior from within the main form doesn't work well.

Any additional thoughts or ideas?

Sounds like ... this could be a limitation when using a Report in a Form ?
As a test - does code in *any* event in the Report execute ?

mx

The open event is the only code that runs. But, when you try to set the Visible property of a text box in the Detail section (for example), it doesn't exist, so the code doesn't execute (Object cannot be found).

Just curious also ... what if this was a subReport in another Report (even if just a blank report). Does the Detail Section code execute then ?

mx

Yes, the code executes fine if it is a subreport in another report.

Is this the first time you have tried this, or is it just not working in this instance ?

This is the first client that has needed code to execute in the subreport. I've used subreports in forms numerous times, but have just not encountered this specific situation before.

The only time I ever had to write VBA code in a subreport is to pull off the alternating greybars, before whatever Access version came out with the Alternate Back Color.

Any manipulation of columns (say last_name comma first_name) I was able to pull off in the query that fed your subreport.

So .. tell us what task dictates VBA code behind 'code to execute in the subreport'.

The user is requesting that they can view an invoice (report) from within a form. That way they can modify data in the form and preview how the printed invoice will appear. They want to hide and show different controls on the report based on the data in each detail line of the report.

Since I did not receive a viable solution, or any particularly helpful comments, I had to abandon what I was trying to accomplish.