In Access 07 command button won't open a specific form

[MarkB]

In previous versions of Access you could build a form with a combo box and a
command button. With the wizard you could have the command button open a
form that relates to the value stored in the combo. So, if combo has
Customer 123 selected, the command button would be able to open the customer
form for that specific customer.

In Access 07 the wizard takes you through the same steps as before, but
fails when you get to the point where it asks how the form with the combo
relates to the 'other' form. The wizard lists all the fields on the Customer
form - but NOTHING on the form with the combo... in the older versions, it
would list the combo as one of the controls you could use to match the two
forms with.

 

[Beth Melton]

It sounds like the combo box is an unbound control. But you can always add
your own Where Condition. View the Embedded Macro the Wizard generated
(access this through the properties of the button), place your insertion
point in the Where Condition Action Argument and press F1 to access Help. It
will give you an example of how to create a Where Condition.

If you still have questions then you might want to post in an Access
specific newsgroup in order to obtain a faster response to your question.
(Around here you need to wait for someone who knows Access to happen upon
your post. )

Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/

 

[MarkB]

It sounds like the combo box is an unbound control. But you can always add
your own Where Condition. View the Embedded Macro the Wizard generated
(access this through the properties of the button), place your insertion
point in the Where Condition Action Argument and press F1 to access Help. It
will give you an example of how to create a Where Condition.

If you still have questions then you might want to post in an Access
specific newsgroup in order to obtain a faster response to your question.
(Around here you need to wait for someone who knows Access to happen upon
your post. )

Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/




Beth,

Thanks for the suggestion. Writing my own WHERE clause is OK for me, but
I'm teaching Access to undergraduate business students and had hoped to use
the wizard (which worked in the earlier versions). We get to Forms fairly
early in the course - too early to be explaining that the wizard didn't work
as advertised, so we'll need to work around it.

I'll take your suggestion to post to a group more Access-oriented.

Thanks,

Mark

 

[Beth Melton]

Thanks for the suggestion. Writing my own WHERE clause is OK for me, but
I'm teaching Access to undergraduate business students and had hoped to
use
the wizard (which worked in the earlier versions). We get to Forms fairly
early in the course - too early to be explaining that the wizard didn't
work
as advertised, so we'll need to work around it.

I'll take your suggestion to post to a group more Access-oriented.

Hi Mark,

A quick check on this and it appears to work with bound controls so I don't
think the Wizard changed, but it could be where it's placed in a form that's
changed. For example it won't be picked up if it's on a subform. I'm not
that familiar with the Wizard functionality in either version. While I teach
Access as well, I tend to train the "how it works first" and then show the
Wizards after they know how to modify what the Wizards create. (My personal
preference, of course. ;-) )

~Beth Melton