[AccessD] VBA question

For Access maybe its down to something like "a macro cannot be edited beyond
what the GUI allows, a VBA procedure can". Is that even completely true?

JB

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
> Sent: Thursday, April 24, 2003 9:28 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] VBA question
>
>
>
>
> > I always looked at macros as "user recorded actions". The only problem
> with that
> > is, how do you record user actions in Access? I think Access
> uses the term
> > "Macro" incorrectly. A "Macro" in Access should be called a
> "Script". Just
> my
> > two cents.
>
> ======I always thought of them strictly as commands, executed
> when needed by
> the user. The recorded thing is a problem since many applications didn't
> have macro recorders at first. Remember 1-2-3? You just entered commands
> into the worksheet, named it, and then executed it from the keyboard -- no
> events.
>
> Susan H.
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>