Printing selection criteria header status

**Vodka** · 17-02-2010

Hello,
Here is my problem, I created a form multiple research from a table created by a query. I have six search criteria via six combox. I get the results in a window lstresults. From a button Btimprimer I print a report with the same fields as lstresults. These steps work perfectly. However I would edit in the header of the state the value of the six search criteria (cmbRechCateg et seq) and statistics.
Here is the code for it

Code:

Option Compare Database

Private Sub chct_Click()
If Me.chct Then
    Me.cbrcct.Visible = False
Else
    Me.cbrcct.Visible = True
End If
RefreshQuery
End Sub
 

End Sub

**Miles Runner** · 17-02-2010

Hello,
To change the settings I use the argument OpenArgs (the latter to open report) by forming a string.
ex imitation of code to the calling form

Code:

Sun mesParam as string
 
if mncrt then
   if mnpar <>"" then
     mnpar = mnpar & vbNewLine:'Move to the line with each criterion
   end if
   mnpar = & mnpar "My test text"
end if

Code:

DoCmd.OpenReport MyReport ,,,,, mnpar:'mnpar must be the last parameter

**Linux-Us** · 17-02-2010

Hello,
In the report you can include the following part of code.

Code:

Sun m_str as string
 
private sub OnOpen()
   if not isnull(I.OpenArgs) then
     m_str =I.OpenArgs
   end if
end sub
 
Public function LireSousTitre() as string
   LireSousTitre = m_str
end function

In the report, preferably in a header section which may have variable height (can grow = true, can shrink = true) define a text field 'Soustitre' with a source: LireSousTitre = ()

**SoftWore** · 17-02-2010

Hello,
The function OpenArgs statement is not valid in Access 2000. Only from the 2003 version. For my part in calling the state I put a text field that contains the title and then in my statement I referred to. It is also possible to use a global variable (according to experts is not advisable but I do not know why) and then referring to it. Only the code must be placed in the event to print if it does not work

**GlassFish** · 17-02-2010

Hello,

Code:

function OpenArgs statement is not valid in Access 2000. Only from the 2003 version.

Good point but from Access 2002 (XP).

For my part in calling the state I put a text field that contains the title and then in my statement I referred to.

This solution works since version 2.0 which is very convenient. It has the disadvantage of binding the state to form, changes the form and your report can be broken without you knowing. The OpenArgs allows the report to remain independent and self sufficient.

**HardWeaR** · 17-02-2010

Hello,

It is also possible to use a global variable (according to experts is not advisable but I do not know why)

The pb of global variables is that they are visible and modifiable throughout the code. It is very easy in a module and change the value to plant and another module, again without knowing which one. So when you have a variable Global and they are touched, it must traverse the entire application to find out where and how it is used. A recommended practice is to hide (make 'private') information which has not be known outside the current module and use parameters to pass information between modules. You can also use a class module in Access or property on a form that presents the variable read-only for everyone to use information and the owner of the change. These concepts are grouped in the literature under the term 'data encapsulation'.