Multiple forms and multiple queries?

[Guest]

I am wondering if the way I am going about this is the only way to do it?
I am creating a query and a form for each of the types of searches a user
may need, and the results show on a form. Then I am puting buttons on a
switchboard to open each form.
I am basicly using the same form and same query but with different critera.
So I am just copying and renaming, changeing the critera and saving.
I am thinking maybe there is a way to change the critera in a query from
options a user chooses on a form or a button? So I can use one form and one
query.

i have searched everywhere for an answer but cant find anything.

Thanks in advance

 

[Rick Brandt]

I am wondering if the way I am going about this is the only way to do
it?
I am creating a query and a form for each of the types of searches a
user may need, and the results show on a form. Then I am puting
buttons on a switchboard to open each form.
I am basicly using the same form and same query but with different
critera. So I am just copying and renaming, changeing the critera and
saving.
I am thinking maybe there is a way to change the critera in a query
from options a user chooses on a form or a button? So I can use one
form and one query.

i have searched everywhere for an answer but cant find anything.

Thanks in advance

Yes you can do all of this with one form based one one table or query.

Have you looked at the built in Filter-By-Form tool? Takes about 5 seconds to
use.

There are numerous other ways to create and apply filters on-the-fly to a single
form with a RecordSource that has access to all of the records.

 

[Albert D. Kallal]

As you are finding out, putting forms! expression in queries can get really
messy real fast.

Even worse, is now that the query is now "married" and attached to that ONE
form. Often, I have a nice query that I could use MANY times for different
reports, and often even that same query could be used for reports...but then
someone comes along and puts in a expression that means the query is ONLY
good when that form is opened.

Worse, is very hard to control things like having 5 combo boxes, but the
user only selects restrictions in 3 of the combo boxes...and wants the other
2 to be ignore.

I could probably write another 10 or pages as to why putting forms
expressions in queries is bad (besides...it makes the queries real ugly, and
hard to read. and, the sql then is not standard anymore (it will not work
with server based systems either).

So, the solution use now is simply to take the values from the form, and
build your own where clause in code. That way, you simply design the reports
(or forms), and attached them to the query, BUT NO FORMS! conditions are
placed in the query.

To "send" the conditions to the report (or form), you simply use the "where"
clause. This is exactly why ms-access has this feature...and it solves a
zillion problems...and will reduce your development costs by a substantial
amount.

Take a look at the following screen shots to see what I mean:

http://www.members.shaw.ca/AlbertKallal/ridesrpt/ridesrpt.html

The code to make those above screens work and launch the report with the
selected restrictions when you hit the "print" button is easy:


dim strWhere as string

' select sales rep combo

if isnull(cboSalesRep) = false then

strWhere = "SalesRep = '" & cboSalesRep & "'"

end if

' select what City for the report

if isnull(cboCity) = false then
if strWhere <> "" then
strWhere = strWhere " and "
endif
strWhere = strWhere & "City = '" & cobCity & "'"
end if

Note how the 2nd combo test is setup. You can add as "many" more conditions
you want. Lets say we have a check box to only include Special Customers. We
can add to our very nice prompt screen a check box to

[x] Show Only Special customers

The code we add would be:

if chkSpeicalOnly = True then
if strWhere <> "" then
strWhere = strWhere " and "
endif
strWhere = strWhere & "SpecialCust = true"
endif

For sure, each combo and control we add to the nice report screen takes a
bit of code, but no more messy then the query builder..and this way, each
query is nice and clean, and free of a bunch of HIGHLY un-maintainable
forms! expressions.

Further, it means you can re-use the same query for different reports, and
have no worries about some form that is supposed to be open. So, a tiny bit
more code eliminates the messy query problem.. For me, this is very worth
while trade.