command button wizard in Access 2007 and macros

[Guest]

Short question:
Why does the Acc2007 control wizard now create macros for command buttons,
instead of code, the way it used to? I thought MS was going to phase out
those old macros. It seems terribly backwards-looking to me. I haven't seen
an official explanation for this.

George

 

[Allen Browne]

The reason MS has beefed up macros is that they don't like VBA. VBA is
unmanaged, so can do stuff that may not be a good idea. So unless the
database is digitally signed or in a trusted location, VBA doesn't run at
all.

To work around this, MS made macros more powerful and easier to use. They
can now have variables (TempVars), and you can see the arguments in macro
design (i.e. not just one line at a time.) They also introduced embedded
macros, which can use error handling.

However, if you are serious about developing non-trivial applications in
Access, you still need VBA.

 

[Guest]

Thanks, Allen. I do, in fact, build apps for my district in Access in vba and
was taken aback by some changes in 2007. I wonder, given the new security
features, that they did not beef up VBA in Access and the other Office apps,
as you pointed out. Granted, it would create larger, more significant
changes, but that has to be the way to go, I think. And I'm also going
through that fix you posted in the other message.
George