| re: Query influenced by combo box value
"Giulio" <giuliastro_NOSPAM_@tin.it> wrote in message
news:bqpgsa$hf1$1@ftp-news.csita.unige.it...[color=blue]
> Hello,
> I have a continuous form with a combo box inside. From the combo box I can
> pick some values which, by the "after-update" event, change some other combo
> box values determined by a query.
> (i.e. I have some tree names and depending on what tree I pick on the other
> combo box I can pick its fruits and other properties)
>
> Now, mine is a continous form, and whenever I pick a value from the first
> combo box the second one correctly shows the updated values, but the first
> combo influences all records' combos in the form.
> This way, following with my trees example, if I change the third tree all
> combo boxes with properties for other trees change showing properties
> related to this tree.
>
> This is the query of the second combo box that depends on the first one
> (IDTree):
>
> SELECT DISTINCTROW TblProps.IDProp, TblProps.PropName, TblProps.IDTree FROM
> TblProps WHERE (TblProps.IDTree=CurrentRecord.IDTree.value)[/color]
Nothing. In a continuous form view there is what appears to be multiple
ComboBox pairs but there is really is only one pair *shown* repeatedly. When
you change the criteria for the query supplying the rows for the second ComboBox
it HAS to influence all of the Combos you see *because there is only one*.
The only thing that can vary from row to row in a continuous form is the DATA
from the RecordSet (or values derived from that data).
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
| 
