Re: Filtering a Number of Comboboxes Before Their Forms are Opened(?)

That is not so. It's not that big a deal to use one table
to filter records in another table and my earlier reply
demonstrated one way. Actually, there are several ways to
do it using the same row source in all installations. The
trick is to decide where to save the installation's Office
value.

If the Office value is saved in a custom database property,
then the query's criteria could use a trivial user defined
function the retrieves the saved value.

Using the Open event to set the combo box's RowSource
property is probably the most efficient, but it's unlikely
enough of a gain to warrant the additional code.
--
Marsh
MVP [MS Access]


J_Goddard via AccessMonster.com wrote:
To do what you are asking requires that the forms be opened in design view,
the combo box sources changed to match the office, and the updated forms
saved. While this can be done programmatically in VBA, it can be a pain.
Much easier would be to set and keep the "Office" value in a table, as
Marshall has suggested, then set the combo box sources in the form On Open
events to suit each office's requirements.


croy wrote:
I'm trying to set up a "switch" in my db such that another
office can get an updated front-end from me, and the first
time they open the mdb, they can select their office,
causing several cbos on various forms to change their
rowsource (or change a criteria in their SQL) so that they
don't have to weed thru so many choices.

I've got a startup form with a cbo for selecting their
office, and I've made it sticky, like it should be. But
now, how to change what they see in the cbos on the other
forms?


.