Form as input to a report

[Paul D.Smith]

Warning: newbie question!

I have my database.
I have a report that currently prompts me for input (say "postcode/zip") and
then produces the required output.

This works but if I want to extend this to a number of fields, it's rather
irritating getting lots of individual popups. Much better would be a
"screen" where I can enter values for various fields and the press "Make
Report". From my delvings on the web, this seems to be possible but I can't
seem to answer the following questions:

1. My current attempt at a Form always shows the first database entry and
anything I change updates that entry - not quite what I had in mind.

2. I can't see how to create the "Make Report" button.

I'm sure this type of question comes up over and over again so please feel
free to say "read this website/Google for this phrase" - I haven't hit the
correct terminology/Google phrase yet!

Thanks,
Paul DS.

 

[Douglas J. Steele]

The form you create shouldn't be bound to a recordset: you should simply
have unbound text boxes that allow you to type in specific values, or
unbound combo boxes (or list boxes) that let you select from lists of valid
values.

You don't require a "Make Report" button: what you want is an "Open Report"
button (the report should already exist.)

Base the report on a query. For criteria in that query, refer to the various
controls on the form you've created (you refer to them as
Forms!NameOfForm!NameOfControl)

Your Open Report button code will be something like:

Private Sub OpenReport_Click()

DoCmd.OpenReport "MyReport"

End Sub

 

[Paul D.Smith]

....snip...

And of course having sent the e-mail, I scan down and spot "using a form to
select the fields in a query", a post designed to almost precisely solve my
problem.

Paul DS.

 

[Paul D.Smith]

....snip...

Doug,

Thanks for that information. As I get more familiar with Access I'm sure it
will mean something to me and all become clear. Fortunately this is a
"quick fix" requirement to turn a large amount of CSV data into something I
can occasionally search so the general solution that I found elsewhere will
suffice for the moment.

When (if) I ever get a quiet few moments, it would be great to get my head
around Access and create a better solution along the lines that you
describe.

Thanks again,
Paul DS.