filtered lists in more than one form

[MikeO]

I have a database that is used in several warehouses that stock different
items. The items are filtered according to the warehouse based on a yes/no
box in the product table.
I want to use the same front end for each warehouse and allow them to see
only their products. Is there a way to select a "location" and have their
products filtered on several forms? fyi....the "products" table is shared so
any changes to products are the same all.

Thank you,
Mike

 

[golfinray]

Have a separate form for each location and filter. Use a query that runs each
form with only the products for that site being pulled by the query.

 

[Dirk Goldgar]

I have a database that is used in several warehouses that stock different
items. The items are filtered according to the warehouse based on a yes/no
box in the product table.
I want to use the same front end for each warehouse and allow them to see
only their products. Is there a way to select a "location" and have their
products filtered on several forms? fyi....the "products" table is shared
so
any changes to products are the same all.

You could have a table in the front-end -- not the back-end -- named
"CurrentLocation", containing a single record with a Location field that is
set to the current location. In the product table (and any other
location-based table), have a Location field. Everywhere else that you want
to see products, but only those for the current location, base forms and
reports on a query that joins the product table to the CurrentLocation table
on the Location field.

 

[MikeO]

That is actually the way I was headed. I will be combining all the locations
into one database with the transactions table for each location separate.
Then a user can see information for any warehouse by selecting the location
from the main menu.

Thanks,
Mike

 

[MikeO]

Thanks for your reply.
I remembered my long range plans of combining all the data into one database
which would be controlled by selecting your location from the switchboard and
then controlled by forms that you have access to.
I appreciate your quick response.

Mike

 

[Dirk Goldgar]

That is actually the way I was headed. I will be combining all the
locations
into one database with the transactions table for each location separate.
Then a user can see information for any warehouse by selecting the
location
from the main menu.

Do you mean to have a separate transactions table for each location? That
strikes me as a bad idea. Not only would you be unable to query across
locations easily, but you'd have to use code continually to change the
recordsources of forms and reports according to the selected location.
Unless, that is, you plan to have separate forms and reports for each
location, in which case you will have multiplied your maintenance burden.