Sending Parameters to Query

[robin9876]

For a query that has two parameters for a start and end date, is it
possible to send the parameters values when the query is used by a
report instead of prompting the user?
I do not want to add the [forms]![myform]![mycontrol] in to the query
as it then makes the query useable from only that one form.

[LeighP]

Well there are options of course.
<Battens down the hatches>

You *could* use global variables and have a function pull the value as the
criteria for your query (wherever it may be opened from). (Not particularly
my preference I hasten to add)

Or perhaps just have a local table that holds criteria for you (dates too
and other criteria ranges perhaps) and retrieve those values in your WHERE
clause. Set those values before opening whatever form or report you wish
and yer off.

Any use?

<ro*******@hotmail.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com...

For a query that has two parameters for a start and end date, is it
possible to send the parameters values when the query is used by a
report instead of prompting the user?
I do not want to add the [forms]![myform]![mycontrol] in to the query
as it then makes the query useable from only that one form.

[Justin Hoffman]

<ro*******@hotmail.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com...

For a query that has two parameters for a start and end date, is it
possible to send the parameters values when the query is used by a
report instead of prompting the user?
I do not want to add the [forms]![myform]![mycontrol] in to the query
as it then makes the query useable from only that one form.

Have you looked at the arguments for DoCmd.OpenReport? You can specify a
filter so it only shows relavant records. This is OK as long as you provide
your users forms and buttons to open the report and do not simply let them
open it from the database window.
Another option is to base the report on a query and re-write the definition
of the query (qdf.SQL) each time. Again - this is for when you write the
UI.