Hi :

Over the past 48 hours or so I have been having some problems with three combo boxes I have placed on a form. I will re-state the situation, and then write what I have uncovered as the problem to see if anyone has a solution:

Situation:

I have three combos>
A. cboCsourcestate
B. cboCfield
C. cboCoption

Combos B & C are fueled by pviews. I can select values for each combo box without a problem. I can scroll through records and all the values stay in focus and things are great. The problem occurs when I close the form and re-open the form. When I do that, the values in the 2nd and 3rd combos of each record do not display the selected values I chose. By not displaying, I mean in the viewable portion of the combo, not in the combo drop down. Note: the control source table for the combos is storing the data I select correctly.

____________________________________________________________________

I decided to take everything apart and locate the source of the problem. I took all the code out of the interactivechange() of the combos... evertyhing. I then ran a series of tests.

To make a long story short, the combos worked perfect (displayed values in combo when I closed and re-opened the form) for regular views and tables.

***** The combos did not work correctly as soon as I placed a pview into the rowsource.*****

That is the problem. I need to use a pview in order to have the combos pull the correct data I need.

Does anyone know why pviews are causing me this problem with my combos >>>? The only thing different between my regular views and my pviews are that I set a WHERE statement. It looks like the following:

WHERE votersfile.cstate = ?thisform.currentstate

Has anyone else had a problem like this?
If it is ok to have pviews as a rowsource of a combo, which I am sure it is, what things do I need to make sure I have set (code!!!) so I am not encountering this problem?

TIA for any input

jason