Printing Subreports

It's the same message, for some reason it's not recognizing the CustNo or QNCLI. I also renamed my report to "Credits' just to make it easier but still it's not working.

Here is a print screen of my form in design view and it's the Command21 button on the report that I am trying to do. I would like to have a command button on all the reports on the form so that the users have a choice of which different reports they need to print as they may not need all of them. The print button on the form in Blue we need to delete

Are customer's individuals? In my company, customers are known more by their names than their numbers, but if you go by Account number, then it does make more sense to use that. Thous I would still use a combo so you are assured that they select a valid account number, and then you don't need to use code to verify it.

We are having a problem here where you know your database and we don't. I can tell that the code:

DoCmd.OpenReport "reportname",acViewPreview,,"[keyfield] = " & Me.keycontrol

works. I use it all the time. But you have to use the correct report name, the correct name for the unique field in the recordsource of the report and the correct name for the control that contains the value you want to filter for.

Now when you say "QNCLI isnt working either." you have to define how its not working. Are you getting the same message or a different one?

Unfortunately searching by customer name wouldn't work because we have many customers with the same name and a lot of times customers do not provide their name on paperwork but only their account #'s. As well the tables we have are files imported from queries run from the As400 so that is why the names differ and relationships had to be made in access.

The database works fine it does the job its meant to do for what we need it for except for when it comes to printing as stated. 

Im sure its all in the expression and this is an area i am a complete novice in. 

Changing CustNo to QNCLI isnt working either.

For examples of the sort of unbound forms Scott is referring to in his last post you might like to take a look at MultiSelect.zip in my public databases folder at:

https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169

Note that if you are using an earlier version of Access you might find that the colour of some form objects such as buttons shows incorrectly and you will need to  amend the form design accordingly.  

If you have difficulty opening the link copy its text (NB, not the link location) and paste it into your browser's address bar.

This little demo file illustrates how to open a report whose results are restricted by means of controls in a form.  It demonstrates means of doing this in a variety of contexts.

For an example of a report opened from a bound form to show data for the current record only, the InvoicePDF demo in the same OneDrive folder illustrates this.  In this case the report's query includes a parameter which references the form's order number, rather than the report being filtered by the WhereCondition argument of the OpenReport method. The reason this method is used is that it also enables the report to be output directly as a PDF file, which is the main purpose of this demo.  Theoretically it would be possible to add the rptIInvoice report to this form as a subreport, and also preview it from the Open Invoice button in the form.

Yes it certainly would. This is another not recommend practice. Key fields and their foreign key equivalents should all have the same names. If there is no CustNo field in the Recordsource of the report, then it would certainly cause a problem try changing it to "QNCLI =" & Text25.

However, I still think you have made a lot more trouble for yourself than necessary. A form that is ONLY used to open a report for preview should be unbound. it should have one (or more) controls to enter criteria and another control to open the report(s). 

In your case, I would use a Combobox to select a Customer by name (but return the customer number) and a button to open the report. Very simple.