[AccessD] VBA question

>From pcwebopedia.com

1) A symbol, name, or key that represents a list of commands, actions, or
keystrokes. Many programs allow you to create macros so that you can enter a
single character or word to perform a whole series of actions. Suppose, for
example, that you are editing a file and want to indent every third line
five spaces. If your word processor supports macros, you can create one that
consists of the following keystrokes:
Move Cursor to Beginning of Line

Move Cursor Down 1 Line

Move Cursor Down 1 Line

Move Cursor Down 1 Line

Insert 5 Spaces

Now you can enter the name of the macro, and the word processor will perform
all these commands at once.

You can also use macros to enter words or phrases that you use frequently.
For example, you could define a macro to contain all the keystrokes
necessary to begin a letter -- your name, address, and a code that inserts
the current date. Then, whenever you write a letter, you just press the
macro key to include the letter header.

In a way, macros are like simple programs or batch files. Some applications
support sophisticated macros that even allow you to use variables and flow
control structures such as loops.

(2) In dBASE programs, a macro is a variable that points to another variable
where the data is actually stored. In most other applications, this would be
called a link.





----- Original Message -----
From: "Bryan Carbonnell" <Bryan_Carbonnell at cbc.ca>
To: <accessd at databaseadvisors.com>
Sent: Thursday, April 24, 2003 10:51 AM
Subject: RE: [AccessD] VBA question


> OK, so let me see if I get your points Scott,
>
> 1) A macro automates the UI, with things like dropping down the menus
visibly and such?
>
> 2) When you record a macro (in Word or Excel) as soon as you stop
recording the macro, it stops being a macro because it's VBA code that gets
recorded?
>
> Bryan Carbonnell
> bryan_carbonnell at cbc.ca
>
> >>> scott.marcus at ae.ge.com 24-Apr-03 10:40:05 AM >>>
> 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
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>