[AccessD] VBA question

OK. I guess what I'm getting at is that a macro is basically automation of the
user interface. When you go beyond that, you are doing scripts or code. I think
that in Word and Excel, it's a macro while you are recording it, but the actions
are converted to code. It's no longer a macro at that point (even tho it is
still called a macro in Word and Excel). I could get into this deeper but see no
reason why. What is this for exactly?

Scott

-----Original Message-----
From: Susan Harkins [mailto:harkins at iglou.com]
Sent: Thursday, April 24, 2003 10: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