M
MarkB
In previous versions of Access I could place a combo box on a form (populate
with a query) and then use a Command Button to open another form related to
the value selected by the user from the Combo... e.g. user selects a Customer
from the combo, clicks the command button and we open the associated Customer
form.
The wizard would ask how the two forms were related - it would list the
Combo for one of the forms and then list the fields on the customer form as
the second form. You would select the Combo from one side and CustID from
the other (Customer form).
The 2007 wizard gets to that same step (everything looks the same), but
lists NO data on the form that has the Combo. It's as if the combo doesn't
exist. If you attempt to code it as an embedded macro, writing the Where
clause, you can select a customer from the combo, hit the command button and
it opens a blank customer form!
I'm teaching Access to freshmen business students. I'd rather not have to
say that we need to work around the wizard as early as week 4. The whole
process looks exactly the same - except for the failure of Access to list
what's on the first form.
Thanks for any help
Mark
with a query) and then use a Command Button to open another form related to
the value selected by the user from the Combo... e.g. user selects a Customer
from the combo, clicks the command button and we open the associated Customer
form.
The wizard would ask how the two forms were related - it would list the
Combo for one of the forms and then list the fields on the customer form as
the second form. You would select the Combo from one side and CustID from
the other (Customer form).
The 2007 wizard gets to that same step (everything looks the same), but
lists NO data on the form that has the Combo. It's as if the combo doesn't
exist. If you attempt to code it as an embedded macro, writing the Where
clause, you can select a customer from the combo, hit the command button and
it opens a blank customer form!
I'm teaching Access to freshmen business students. I'd rather not have to
say that we need to work around the wizard as early as week 4. The whole
process looks exactly the same - except for the failure of Access to list
what's on the first form.
Thanks for any help
Mark