J
JohnE
I am having a dilemma with several forms and several combo
boxes. I will explain and use generic names to simplify
the explanation.
I have 2 forms, FormA and FormB. FormA is the first form
to open and remains open as it acts as the "master form".
It has the client name and some other information on it.
On FormA I have a combo box (ComboA1) with 3 names in it
from a value list (DivisionA1, DivisionA2, DivisionA3).
From FormA you can open FormB thru a drop list menu.
FormB shows client information based on what client is
listed in FormA (not the combo box mentioned above). On
FormB I have a combo box (ComboB1) that displays names of
people from the 3 divisions. Also on FormB is an unbound
textbox (txtboxB1) that displays the value from ComboA1 on
FormA. ComboB1 on FormB displays the names of those from
the 3 divisions based on what txtboxB1 has in it.
All of this info is generally added when a new client is
added. But, there are situations in which ComboA1 on
FormA is changed. If that is the case, then ComboB1 on
FormB must also be changed to the correct person. When
the info in FormA changes, FormB does a requery. This
updates the info in txtboxB1. It will also change the
names in ComboB1.
Now comes the dillemma. ComboA1 on FormA is changed,
FormB get requeried, txtboxB1 changes, ComboB1 changes,
but when I try to select a name in ComboB1 I get a ding
and cannot make any change. The same is true if I go back
to ComboA1 on FormA I'll also get a ding.
I can get this all to work by using an odd combination of
requery, refresh, and save. All SELECT statements for
ComboB1 are in FormB's OnCurrent event. All the people
names, etc for ComboB1 on FormB are all on one table,
tblPersonnel.
I am going bonkers trying to figure out why I get the
dinging noise and the name will not select. The
information on FormB that I am trying to change is on the
same table as the info in FormA that is changing.
I am open to suggestions or ideas as to correct or even
make a modification of how this all interacts.
Thanks in advance to anyone who responds.
*** John
boxes. I will explain and use generic names to simplify
the explanation.
I have 2 forms, FormA and FormB. FormA is the first form
to open and remains open as it acts as the "master form".
It has the client name and some other information on it.
On FormA I have a combo box (ComboA1) with 3 names in it
from a value list (DivisionA1, DivisionA2, DivisionA3).
From FormA you can open FormB thru a drop list menu.
FormB shows client information based on what client is
listed in FormA (not the combo box mentioned above). On
FormB I have a combo box (ComboB1) that displays names of
people from the 3 divisions. Also on FormB is an unbound
textbox (txtboxB1) that displays the value from ComboA1 on
FormA. ComboB1 on FormB displays the names of those from
the 3 divisions based on what txtboxB1 has in it.
All of this info is generally added when a new client is
added. But, there are situations in which ComboA1 on
FormA is changed. If that is the case, then ComboB1 on
FormB must also be changed to the correct person. When
the info in FormA changes, FormB does a requery. This
updates the info in txtboxB1. It will also change the
names in ComboB1.
Now comes the dillemma. ComboA1 on FormA is changed,
FormB get requeried, txtboxB1 changes, ComboB1 changes,
but when I try to select a name in ComboB1 I get a ding
and cannot make any change. The same is true if I go back
to ComboA1 on FormA I'll also get a ding.
I can get this all to work by using an odd combination of
requery, refresh, and save. All SELECT statements for
ComboB1 are in FormB's OnCurrent event. All the people
names, etc for ComboB1 on FormB are all on one table,
tblPersonnel.
I am going bonkers trying to figure out why I get the
dinging noise and the name will not select. The
information on FormB that I am trying to change is on the
same table as the info in FormA that is changing.
I am open to suggestions or ideas as to correct or even
make a modification of how this all interacts.
Thanks in advance to anyone who responds.
*** John