[AccessD] VBA question

Hmmm, I wouldn't say that.  Excel and word Macros are more like scripts,
because a script is a programming language.  A lot of 'macros' that I have
dealt with in Non Microsoft situations all were step by step procedures,
where the items allowed were pretty generic, no where near as 'broad' or
capable as VBA.  (Like a macro in good old BBS dialing software (forgot the
correct term at the moment....but QModem was an example, my personal
favorite was called Boyan.  Boyan allowed for 'macros' that would send
whatever commands you listed, when you hit a key group.)).

Drew

-----Original Message-----
From: Marcus, Scott (GEAE, RHI Consulting)
[mailto:scott.marcus at ae.ge.com]
Sent: Thursday, April 24, 2003 6:42 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.

Scott

-----Original Message-----
From: Susan Harkins [mailto:harkins at iglou.com]
Sent: Wednesday, April 23, 2003 3:43 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] VBA question


Drew, I was thinking along similar lines this morning, but came up with -- a
macro is something the user executes on purpose, whereas VBA procedures are
executed programmatically -- either through event or some other procedure
call. How's that?

Susan H.


> It's really a matter of where you are coming from.  If you are talking
about
> code within the VBE, then macro is an incorrect term, because you are
using
> functions and subs.  However, if you are talking about the Excel GUI, then
> macro IS the correct term, when you are referring to a sub that the Excel
> user can use.
>
> Drew
>
> -----Original Message-----
> From: Susan Harkins [mailto:harkins at iglou.com]
> Sent: Tuesday, April 22, 2003 8:02 PM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] VBA question
>
>
> I know the word is a hold over from earlier Basic versions, but I wouldn't
> use the term macro to describe a VBA procedure, whether it's a sub or
> function -- is there something else in Word and Excel? I'm not familiar
with
> the structure if there is.
>
> I know the Excel expert at Cobb continued to use the term for eons after
VBA
> and the VBE showed up. I argued with him on occasion. We produced a VBA
> product together and we had a lot of trouble trying to use consistent
> language. :)
>
> Susan H.
>
>
> > ...don't agree that its accurate Bryan ...one hell of a difference
between
> a
> > macro and VBA :(
> >
> > William Hindman
> > "All it takes for evil to prevail is for good men to do nothing." Edmund
> > Burke
>
>
> _______________________________________________
> 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
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com