macros v vba in Access

D

Dave F

Can someone explain to me the distinction between macros and VBA in Access?
I'm coming from the Excel world, where these terms are used interchangeably.
Access people seem to think of them as distinct concepts.

Thanks for any insight.

Dave
 
W

Wayne-I-M

Hi Dave

I think many people will answer your post with ideas, but for me a big
advantage for using vba over macros is that with vba you have the possibility
of doing "stuff" when there is an error.

Another thing is that there are many, many more "items and actions" that can
be performed in vba as the macro dropdown-list of available "stuff" is
limited and the list of "stuff" that need doing in a DB is not.

This said I have some (5) macros on a recent DB as they are much simpler for
users to understand. I have shown the admin manager how to alter them if
needed. It will let me get on with more important things like having a cup
of coffee.

So - vba to get the DB to do what you and the client what it to do. Macros
to allow user to change "stuff" when needed without going into the vba and
really messing things up.
 
R

Rick Brandt

Ofer said:
Check this link on "Microsoft Access Macros vs. VBA - Why Use Macros"

http://www.databasedev.co.uk/macros-in-access.html

It's not clear in that article whether he is talking about Access 2007 only.
He describes macros as being "recorded steps that you perform". That is how
they work in Excel and Word, but unless Access 2007 changed this it has
never been the way you create macros in Access.

If Access 2007 has not changed this then that tells me that the author
actually has very little knowledge of Access macros and is not a good source
for information on them.
 
P

(PeteCresswell)

Per Dave F:
Can someone explain to me the distinction between macros and VBA in Access?
I'm coming from the Excel world, where these terms are used interchangeably.
Access people seem to think of them as distinct concepts.

They are.

In Access, macros are higher-level objects that you specify in a "Macro" editing
screen.

VBA is... well... VBA. i.e. What you're used to thinking of as "Macros" in
Excel.

My position since very early in the game has been "Real programmers don't use
macros".

First reason that comes to mind is that there's no error trapping in macros.

Second is one-stop shopping: I want all my routines in one place.
 
I

i_takeuti

(PeteCresswell) said:
Per Dave F:

They are.

In Access, macros are higher-level objects that you specify in a "Macro"
editing
screen.

VBA is... well... VBA. i.e. What you're used to thinking of as "Macros"
in
Excel.

My position since very early in the game has been "Real programmers don't
use
macros".

First reason that comes to mind is that there's no error trapping in
macros.

Second is one-stop shopping: I want all my routines in one place.
 
Top