filter in report based on table's filter

[JuniorWoodchuck24]

If you filter your table and you're pulling fields into your report based on information in the table how would you apply the filter in the report?

Table has all data, but you filter it for example just use cars:
Initially has all cars so when you open report it pulls in all info
You only want Mustangs to show up in your report, how would you apply this filter to your report?

 

[namliam]

Try doing a search on "search forms" and see if you can go from there.

 

[JuniorWoodchuck24]

if you are referring to using a filter on a form, that won't work in my case. i use forms to write to tables. since a form can be made more user friendly and have more functionality.

user enters info into a form - writes info to table - report pulls info from table

is basically how my setup works. there has to be some form of VBA code that will pull info from the table in a filtered format.

was thinking about adding an InputBox in the report when the user opens the report that prompts them to call there type and from that it just pulls info from the table based on the selection the user made. my only thing is i lack the coding knowledge to pull all data per filter. assume you would call a if statement based on input = type and then pull, but i'm not sure what the code is exactly.

 

[namliam]

Table has all data, but you filter it for example just use cars:
Initially has all cars so when you open report it pulls in all info
You only want Mustangs to show up in your report, how would you apply this filter to your report?

Try doing a search on "search forms" and see if you can go from there.
Try doing a search on "search forms" and see if you can go from there.
Try doing a search on "search forms" and see if you can go from there.
Try doing a search on "search forms" and see if you can go from there.

if you are referring to using a filter on a form, that won't work in my case.

Quick to judge arent we?

since a form can be made more user friendly and have more functionality.

Exactly, since a form can be made more user friendly
exactly, since a form can be made more user friendly
since a form can be made more user friendly
since a form can be made more user friendly
since a form can be made more user friendly

Yes, so use a form to make your filter, then send the filter to the report.
If you search the forum for .... you might find some samples that utilize sending a filter and/or where clause to a form/report and addapt that to suite your needs.

 

[JuniorWoodchuck24]

it seems like most people in this forum that respond to help have one way of doing things and choose not to show examples why another option doesn't work or why the one they support is better. they just automatically assume that their way is the "only way." personally i think making a user enter information into a form to write to a table to pull up into a report to print is keeping it simple for them. now if i personally was using the database yah i wouldn't mind going from form - table - form - report. but getting someone who has little to no knowledge at all about access to go from form-table-form-report you confuse them because they ask "why do we have to go back to a form to filter out the report?" when you can just make another table that the report pulls from.

btw i'm not quick to judge and the redundant quotes are quite immature. i know that i can make a command button that you click to filter and open a report. i'm just trying to think outside the box to see if other options are available.

 

[namliam]

it seems like most people in this forum that respond to help have one way of doing things and choose not to show examples why another option doesn't work or why the one they support is better. they just automatically assume that their way is the "only way."

These people have years of experience to draw these conclusions upon

form - table - form - report.

How is this different from your proposed solution of Form - Table - Input box - Report???

It doesnt even need to be a seperate form, you can make only one form, but your basing it of a SAMPLE where you can see how it works....

but getting someone who has little to no knowledge at all about access to go from form-table-form-report you confuse them because they ask "why do we have to go back to a form to filter out the report?" when you can just make another table that the report pulls from.

ANOTHER table ?? NO, 1 table your source, NOT another table surely not?

btw i'm not quick to judge and the redundant quotes are quite immature. i know that i can make a command button that you click to filter and open a report. i'm just trying to think outside the box to see if other options are available.

Sorry having a BAD day, shouldnt have repeated, but if you dismiss something without even trying/looking at it ... it gets my goat.

You can -quite easily- make a input box or something to feed to the report.
However this will pose problems, cause issues and make life in general hard on yourself and the users of your database.

I.e This time you want to filter on Mustangs, next time Fords.
Then the next question is build in year 2002
Or in "mint condition"
Or "value between 10.000 and 12.345"

And so on and so forth, like you said the form is much more elegant and "since a form can be made more user friendly".
So instead of making a command button that opens the report, you use a command button to open the search form, then have the user enter their search parameters what ever they need.
The form will then automagicaly transpose that into a required filter on your report and open it or print it or what ever for the user to do with as they see fit.

The form can also contain i.e. Comboboxes and listboxes, where as a input box or 'random popup' simular to what your proposing will not be able to do that.
As a result a user will enter "Mutsangs" or "Mustang" and wonder why the hell the report dont return anything, where the combobox would have prevented that issue.

Trust me, search form