You can also use parameterized views for the rowsource of your combo boxes. Then just requery when needed.

>I have a data file of employees at multiple companies working for multiple locations in multiple departments. The data is normal with codes for the company/department/location and corresponding lookup tables.
>
>The client wants a view screen where he can have a dropdown of company, location, and department, click into each and cut the query down (this is a screen used to find an employee when the hq person is unsure of where they work). Ive given him this product. He gets a query of everyone and when he selects a company the query is requeried and cut down to that company.
>
>
>He now wants the second drop down box (location) to be cut down when the company is selected to only locations that actually have an employee in that company in the big query (which is a logical request they have many companies and hundreds of locations).
>
>
>He likewise wants the third dropdown box cut when the location is selected to have just departments with an employee in them.
>
>I figure I'm going to have to populate the dropdowns with queries and requery against the main cursor. Is that right? Any ideas?
>
>TIA
>Chris