I have created a form similar to the "Customer Orders" in Northwind sample.
User selects a customer from a combo box and the subform shows all their
orders. A second subform will show the details of any specific order
selected. Everything works except that the first order that shows up for a
customer has its customer name changed to the next customer selected.
Basically, instead of just selecting what customer to view, it is assigning
the new customer to the first order showing in the subform. Everything else
seems to be working fine.

Any thoughts? Thanks
Sharon

Let me guess - You set the .ControlSource of the comboBox to a field in the
underlying table? Delete out the value of the .ControlSource. This will make
the comboBox an unbound field and should stop the updates.

Anytime that you're using Query By Form, the controls used to capture the
criteria should always be unbound. Obviously, the .ControlSource property is
not required.

"sharontodd" wrote:

> I have created a form similar to the "Customer Orders" in Northwind sample.
> User selects a customer from a combo box and the subform shows all their
> orders. A second subform will show the details of any specific order
> selected. Everything works except that the first order that shows up for a
> customer has its customer name changed to the next customer selected.
> Basically, instead of just selecting what customer to view, it is assigning
> the new customer to the first order showing in the subform. Everything else
> seems to be working fine.
>
> Any thoughts? Thanks
> Sharon
>

That's it. Along with changing the Link Master Field to the name of the
combo box.

Thanks!!!!

"David H" wrote:

> Let me guess - You set the .ControlSource of the comboBox to a field in the
> underlying table? Delete out the value of the .ControlSource. This will make
> the comboBox an unbound field and should stop the updates.
>
> Anytime that you're using Query By Form, the controls used to capture the
> criteria should always be unbound. Obviously, the .ControlSource property is
> not required.
>
> "sharontodd" wrote:
>
> > I have created a form similar to the "Customer Orders" in Northwind sample.
> > User selects a customer from a combo box and the subform shows all their
> > orders. A second subform will show the details of any specific order
> > selected. Everything works except that the first order that shows up for a
> > customer has its customer name changed to the next customer selected.
> > Basically, instead of just selecting what customer to view, it is assigning
> > the new customer to the first order showing in the subform. Everything else
> > seems to be working fine.
> >
> > Any thoughts? Thanks
> > Sharon
> >