Really need help with 2010 Macros

[Tablerone]

Hi, I really need people who understand the 2010 Macro Builder and how to use Macros with "After Update" events.

MACRO BUILDER IS THE ONLY TOOL AVAILABLE IN 2010 WEB DATABASES. Please don't reply with a load of code and say you missed that bit.

I need to use it (2010 Macros) to create the style of "After Update" events that allow you to build cascade combo boxes. In the past I've done this with a little code, eg the Private Subs on this page:
http://www.fontstuff.com/access/acctut10.htm



The idea is (I hope many advanced users should be familiar with it, if not you can probably pick up the idea very easily): Two combo boxes: cboCountry; cboRegion. I select Mexico, After Update event then narrows the choices in cboRegion to the Mexican ones. If I change the record to have Country: Canada, this (via an "After Update" event) updates the contents of cboRegion with Canadian regions only, and pops cboRegion open to remind the user that now they've made a new choice with Country, they'll also need a new selection for Region.

Now, how to get this job done with Macros (eg in a Web Database where this is the only tool available)? Please tell me even if you think it is obvious.

[June7]

Haven't done a web database and don't use macros but as I understand them, and I just tested, this should work. Comboboxes are set as single column. The RecordSource for cboRegion needs to be an SQL (or reference to a saved Access query) that has reference to the cboCountry as filter criteria. Then the AfterUpdate for cboCountry is an embedded macro with:

Action: Requery
Arguments: cboRegion

[Tablerone]

Thank you very much.

At first glance your answered seemed too short. But then I realised that although I had missed it first time Requery was there as one of the Macro options, and this was all I needed really as far as Macros where concerned.

Then I remembered (because my code really used to be very limited, and even that got very rusty) that the type of code you use in the "Property Sheet" fields (like Row Source) was called SQL code, looked at how a simple VBA code WHERE statement I'd seen elsewhere could be adapted, the SQL style came back to me, and after a couple of rounds of error messages and corrections...

... I have my working cascade! Very happy thanks. Much easier than I thought. From where I'm starting Access looks a bit intimidating at times. When you can't do something it seems so frustrating, then once you've done it you almost wonder why you ever had any trouble.