I've got a little timekeeping system that allows the user to enter task
descriptions, start/stop times and then select "Project" from a combo box.

I'd like to do some analysis on the data, and allocating tasks to sub-project's
seems necessary.

Problem is that in a continuous list, all the combo boxes behave the same.   

So if I make cboSubProject.RowSource tb a query that includes only sub-projects
under the project selected in cboProject, the sub-projects in other rows on the
screen come and go as cboSubProject's list changes.

Anybody got a strategy for situations like this?

Am I describing the scenario clearly enough?
-- 
PeteCresswell

Hi Pete,

Synchronized combo boxes on Continuous form

    Tip #16: Data in a combo box control on a continuous form/datasheet 
disappears
    http://www.fmsinc.com/free/tips.html#tip16foraccess


Contributed by Sandra Daigle (3/10/2006 in microsoft.public.access):
http://groups.google.com/group/microsoft.public.access/browse_frm/thread/e033253ffea2b09f/718a00e1deccf74f?

<Begin Quote>
The problem you are seeing is due to the fact that there is really only one 
combo control - it is just displayed multiple times. So whatever you have for 
current rowsource will apply to all rows. This makes it difficult to use 
synchronized combos on continuous forms. However, there is a fairly easy 
workaround. To create the effect of a synchronized combo in a continuous form 
create another textbox control, include the display column of the combo in 
the Recordsource query of the form (join the foreign table and drag in the 
column). Position and size the new textbox so that you can place it directly 
over the combo box allowing only the down-arrow portion of the combo to show.

Create a GotFocus event for the textbox that only does a SetFocus to the 
combo.

This will create the effect that you are wanting - the correct display value 
will always show even though the value itself might not be fit the criteria 
that is in effect based on the current record.

Here's a KB Article that explains the problem
    (ACC2000:) Combo Box in Continuous Form Shows Incorrect Data
    http://support.microsoft.com/?id=208866

Here's a link to my sample database that offers several different 
alternatives for displaying this type of data including the technique 
described above:

    http://www.daiglenet.com/msaccess.htm

</End Quote>


Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

"(PeteCresswell)" wrote:

> I've got a little timekeeping system that allows the user to enter task
> descriptions, start/stop times and then select "Project" from a combo box.
> 
> I'd like to do some analysis on the data, and allocating tasks to sub-project's
> seems necessary.
> 
> Problem is that in a continuous list, all the combo boxes behave the same.   
> 
> So if I make cboSubProject.RowSource tb a query that includes only sub-projects
> under the project selected in cboProject, the sub-projects in other rows on the
> screen come and go as cboSubProject's list changes.
> 
> Anybody got a strategy for situations like this?
> 
> Am I describing the scenario clearly enough?
> -- 
> PeteCresswell

Per Tom Wickerath <AOS168b AT comcast DOT net>:
>owever, there is a fairly easy 
>workaround. To create the effect of a synchronized combo in a continuous form 
>create another textbox control, include the display column of the combo in 
>the Recordsource query of the form (join the foreign table and drag in the 
>column). Position and size the new textbox so that you can place it directly 
>over the combo box allowing only the down-arrow portion of the combo to show.
>
>Create a GotFocus event for the textbox that only does a SetFocus to the 
>combo.
>
>This will create the effect that you are wanting - the correct display value 
>will always show even though the value itself might not be fit the criteria 
>that is in effect based on the current record.

Thanks.   That was the workaround I was trying to recall.

I'm going to assume that's the "Good-Right-And-Holy-Path".
-- 
PeteCresswell