Firstly I think you are using the term 'subform' incorrectly. A subform is a form which is embedded in a parent form, and is usually, but not necessarily, linked to the parent form by means of the subform control's LinkMasterFields and LinkChildFields
properties. You appear to be referring to a form which is opened independently of the calling form.
As regards passing parameters, it depends what you mean by 'parameters'. If you mean criteria by which the form is filtered to a subset of rows, then the OpenForm macro action includes a WhereCondition argument. This is a string pression which can
evaluate to True or False for each row in the form's RecordSource query or table, e.g. to filter an Orders form to orders by the customer currently selected in a calling form the expression would be along the lines of "CustomerID = " & [Forms]![Customers]![CustomerID].
If, on the other hand, by 'parameters' you mean values passed to the form which are then used by code in the form's module, the OpenForm macro action does not, as far as know, include an equivalent of the VBA OpenForm method's OpenArgs argument, so you would
have to use VBA for this. If you want to pass multiple arguments, then take a look at Args.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.
This little demo file illustrates the use of a module, originally developed by Stuart McCall to pass multiple arguments, and later extended by me to include the ability to pass named arguments.
As you appear to be willing to use VBA, I'm puzzled by why you should want to use a macro at all for this.
Ken Sheridan, Stafford, England
