Making Query Criteria displayable on a report? (Access 2000)

[BlueChicken]

I made a query to pull records by their date. (Criteria: Between [Start Date] And [End Date])

Now I was wondering if on the report I am making for the data pulled by the query if I could somehow make the data entered into the criteria (pop ups before the report is loaded) appear on the report itself.

 

[pbaldy]

You can use the bracketed text in a textbox for display:

=[Start Date]

or even

="Between " & [Start Date] & " And " & [End Date]

The bracketed text must match what was used in the query.

 

[BlueChicken]

You can use the bracketed text in a textbox for display:

=[Start Date]

or even

="Between " & [Start Date] & " And " & [End Date]

The bracketed text must match what was used in the query.

By doing that it only makes you enter the criteria twice. It does display but twice is not fun - also it displays however you type it in - not in an actual date format. (I mean you can type any of the following and get results but all look informal and not right on a report with words:
01-08-09 & 31-08-09, Aug 1 & Aug 31, etc with combinations of each. I want all the dates to display in medium date format to match the rest of the report (dd-Mmm-yy))

 

[pbaldy]

Did you try it? It will not ask twice unless the text doesn't exactly match.

Most of us don't use bracketed criteria, because of the lack of control. We have the user enter criteria on a form, so we can check what they've input before running the report. You can try the Format() function on the bracketed input if you want.

 

[BlueChicken]

Did you try it? It will not ask twice unless the text doesn't exactly match.

Most of us don't use bracketed criteria, because of the lack of control. We have the user enter criteria on a form, so we can check what they've input before running the report. You can try the Format() function on the bracketed input if you want.

Ok, you only have to enter it once now... but I don't understand what you mean by Format() function. I tried formatting the text box but that doesn't make a difference. I don't want to have an entry mask for the date since everyone I know enters dates differently so I don't want that to change (also I wouldn't know how to change that to begin with)

 

[pbaldy]

Completely untested, as I never let users enter dates "any way they want", but try this in the report:

=Format([Start Date], "dd-Mmm-yy")

I generally use an input mask where the users just type 6 digits: mmddyy, so today they are entering 082809. That was actually driven by users, not me, as it's easy for "head-down" data entry users. I often include a date picker (not ActiveX) next to the textbox so they can pick dates from a calendar instead.

 

[BlueChicken]

Completely untested, as I never let users enter dates "any way they want", but try this in the report:

=Format([Start Date], "dd-Mmm-yy")

I generally use an input mask where the users just type 6 digits: mmddyy, so today they are entering 082809. That was actually driven by users, not me, as it's easy for "head-down" data entry users. I often include a date picker (not ActiveX) next to the textbox so they can pick dates from a calendar instead.

Well the code you just gave gives an error saying there is no operator.

And as for the dates, mostly there are only two people entering information. Everyone else is only going to enter dates to search for information... and I just can't seem to stick with one way of entering dates. I had tried having input masks in several of the other forms in the database and I only found it incredibly annoying and troublesome.