I use VBA almost exclusively. Macros are fine for teaching people who aren't "programmers" how to think in terms of program flow, but any serious developer sticks pretty much to VBA.

Id agree with Rich, one good thing about macros is you can convert them to VBA with the click of a button, so a good way to learn how a flow can become code.
But once you see the power of VBA youll never turn back.

I have a slightly different viewpoint. I used to code many years ago when we had those wonderful user friendly languages. So logic is no problem, but I find VBA syntax somewhat hard to master. I don't have a lot of time to learn it. I use VBA when I have no other choice and typically I copy code someone else has done & modify it. I use Macros a lot. I find them easy, although a few are tough to get right ( like export to PDF with a filter) but its amazing what you can do with them. I looked briefly at data macros ( apply to tables only) but have not used them yet. I think if you have the time too learn VBA its a good way to go. But don't knock macros! You can implement a lot fast and easy by using them.

I'm definitely not knocking macros. They certainly have their place. I do this for a living, and I've been a programmer since I was 8 years old, so I love coding. But yes, macros are sometimes the best solution for the non-developer or even the casual user who wants to automate things. I initially had planned on going much deeper in my "Advanced" series with macros, mostly because Microsoft used them in Web Databases which were "the thing" at the time. Then Microsoft dropped Web Databases, so I stopped covering macros and switched to VBA.

Thanks for your input. I tend to agree I myself don't use macros unless pressed to make changes to the database quickly. After that i will go back and use VBA to do it that way. Thank you all for your comments.