Limit content of combo box

[Mark]

All,
I have read the article on the MVP site regarding this topic
(http://www.mvps.org/access/forms/frm0028.htm) but I am having some problems
implementing it.
I have a lookup table which consists of :
[ID] = Number (CompoundKey)
[ProductType] = Text (CompoundKey)
[Product] = Text

I then have another table which will store the values of [ProductType] and
[Product] which have been selected by the user.

In the AfterUpdate event of the ProductType combo, I requery the product
combo which uses the value selected from the ProductType combo as a
parameter for the Products rowsource.

This works fine in a SingleForm environment but changes the values in the
product combo in a continuous form. The values are correct within the table
but are confusing on the form.

Is there a way in which I can just requery the current record's combo rather
than every instance of the combo displayed on the form?

TIA,

Mark

[Anthony England]

"Mark" <ma*********@ntlworld.com> wrote in message
news:vy*****************@newsfe6-win.ntli.net...

All,
I have read the article on the MVP site regarding this topic
(http://www.mvps.org/access/forms/frm0028.htm) but I am having some
problems implementing it.
I have a lookup table which consists of :
[ID] = Number (CompoundKey)
[ProductType] = Text (CompoundKey)
[Product] = Text

I then have another table which will store the values of [ProductType] and
[Product] which have been selected by the user.

In the AfterUpdate event of the ProductType combo, I requery the product
combo which uses the value selected from the ProductType combo as a
parameter for the Products rowsource.

This works fine in a SingleForm environment but changes the values in the
product combo in a continuous form. The values are correct within the
table but are confusing on the form.

Is there a way in which I can just requery the current record's combo
rather than every instance of the combo displayed on the form?

TIA,

Mark

Whatever you do to one combobox in a continuous form, you do to them all -
there is only one control but displayed multiple times. If you are still in
any doubt, try running code like this:
Me.cboMyComboBox.BackColor = vbRed
And suddenly you see that each copy of the control turns red.

So what can you do? The easiest thing might be to have another popup form
to do this selection.

[Mark]

Hi Anthony,

Many thanks for your prompt reply. If that's the case (which I thought it
may be), I have a got at your suggestion.

Thanks again,

Mark

"Anthony England" <ae******@oops.co.uk> wrote in message
news:dv**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...

"Mark" <ma*********@ntlworld.com> wrote in message
news:vy*****************@newsfe6-win.ntli.net...

All,
I have read the article on the MVP site regarding this topic
(http://www.mvps.org/access/forms/frm0028.htm) but I am having some
problems implementing it.
I have a lookup table which consists of :
[ID] = Number (CompoundKey)
[ProductType] = Text (CompoundKey)
[Product] = Text

I then have another table which will store the values of [ProductType]
and [Product] which have been selected by the user.

In the AfterUpdate event of the ProductType combo, I requery the product
combo which uses the value selected from the ProductType combo as a
parameter for the Products rowsource.

This works fine in a SingleForm environment but changes the values in the
product combo in a continuous form. The values are correct within the
table but are confusing on the form.

Is there a way in which I can just requery the current record's combo
rather than every instance of the combo displayed on the form?

TIA,

Mark

Whatever you do to one combobox in a continuous form, you do to them all -
there is only one control but displayed multiple times. If you are still
in any doubt, try running code like this:
Me.cboMyComboBox.BackColor = vbRed
And suddenly you see that each copy of the control turns red.

So what can you do? The easiest thing might be to have another popup form
to do this selection.