L
Lele
My table called Patterns is connected to my table PatternFabricColor in a one
to many relationship. Both tables have an autonumber as their primary key. I
need to be able to select the primary key from the patternFabricColor table
when entering a line item on an order. I also need to be able to add a new
PatternFabricColor if the pattern is there but not the FabricColor, and
finally if the pattern has not yet been entered I want to open a form, in
response to the not on list event. This form is created and set up
(patterns) with a subform (PatternFabricColor) in a one to many relationship
and works fine.
It seems to me the best way for my order entry lines to work is with 2 combo
boxes: the first allows the user to select the pattern and the send is
filtered by the choice the user makes in the first combo box. I have written
a query which with the following parameter
[forms]![orderentry]![orderLineItems]![PatternCbx]. It works ok to a point.
Here's the problem.
When I am in the data entry form, and I select my pattern from the 1st drop
down box, the second box correctly presents the filtered choices; however,
when I make a selection, I am "bleeped" and told there is no matching
PatternFabricColor in the PatternFabricColorTable.
When I open the query that underlies my data entry line subform, I have the
same problem if I enter the pattern name first and then try to enter the
patternFabricColor. However, if I change the the data entry sequence and
enter the PatternColorName first, everything is fine and the form makes the
appropriate matches, looks up and completes the pattern side of the
relationship.
I don't know what is going on, but I really would like the user interface
should work the way I am suggesting. My list of patterns is already large
and when you add the patternFabricColor choices it will get tough to find the
appropriate entry.
I hope I have explained the problem clearly enough. Thanks to anyone who
can offer some help or ideas.
to many relationship. Both tables have an autonumber as their primary key. I
need to be able to select the primary key from the patternFabricColor table
when entering a line item on an order. I also need to be able to add a new
PatternFabricColor if the pattern is there but not the FabricColor, and
finally if the pattern has not yet been entered I want to open a form, in
response to the not on list event. This form is created and set up
(patterns) with a subform (PatternFabricColor) in a one to many relationship
and works fine.
It seems to me the best way for my order entry lines to work is with 2 combo
boxes: the first allows the user to select the pattern and the send is
filtered by the choice the user makes in the first combo box. I have written
a query which with the following parameter
[forms]![orderentry]![orderLineItems]![PatternCbx]. It works ok to a point.
Here's the problem.
When I am in the data entry form, and I select my pattern from the 1st drop
down box, the second box correctly presents the filtered choices; however,
when I make a selection, I am "bleeped" and told there is no matching
PatternFabricColor in the PatternFabricColorTable.
When I open the query that underlies my data entry line subform, I have the
same problem if I enter the pattern name first and then try to enter the
patternFabricColor. However, if I change the the data entry sequence and
enter the PatternColorName first, everything is fine and the form makes the
appropriate matches, looks up and completes the pattern side of the
relationship.
I don't know what is going on, but I really would like the user interface
should work the way I am suggesting. My list of patterns is already large
and when you add the patternFabricColor choices it will get tough to find the
appropriate entry.
I hope I have explained the problem clearly enough. Thanks to anyone who
can offer some help or ideas.