[AccessD] VBA question

I think the 'recording' of a macro is just a natural evolution in macros.  A
macro is meant to be a simple method of automation available to the common
user.  In Access, this allows the beginning developer to include simple
automation and pratically any 'user' to automate tasks in a 'developed'
database.  In Excel and word, you are actually in 'design' mode when you
have a document open, so the environment is far more complex, so it's either
create a 'stepped' macro, with a HUGE list of commands, or allow for
'recording'.

Drew

-----Original Message-----
From: Susan Harkins [mailto:harkins at iglou.com]
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