Richard, the recent question about macros prompted me to ask. In earlier versions of Access, when I let the command button wizard create procedures for me, it created VBA code. In the 2010 version (and maybe 2007, don't remember) it creates macros. I'm hoping that this is not a move away from VBA on Microsoft's part? Do you still recommend using VBA over macros? Is there a place to use macros for experienced developers?

---

Reply from Richard Rost:

Yes, I still do recommend VBA over macros. The wizard now creates something called an EMBEDDED MACRO, which is stored right in your form. The benefit of an embedded macro is that they're GUARANTEED TO BE SAFE. This way malicious coders can't hide something potentially dangerous in the code behind a form and send it out. You run it, and all of the sudden your hard drive is erased (which is possible with VBA). You can open a database you get from someone else and the code behind the forms and reports will still work even if you don't click the "enable" button when you get the security warning upon opening.

PLUS, embedded macros FOR THE MOST PART work if you're going to upload your database to a Sharepoint server for use on the web. There are a few features that don't work, but pretty much all of the popular functions do.

Now, macros have come a long way since earlier versions of Access, and I'll be spending some time on them in the Advanced level classes. They have their place. Obviously if you're building a database you plan on sharing with the world online OR you're planning on porting your database up to Sharepoint, you want to use embedded macros whenever possible.

For the rest of us who are building old-school databases for in-house use (on a LAN) where all of the users trust us, and you're NOT going to put the database online, I prefer VBA myself.

Hope this answers your question. :)