Bob Gajewski
bob at renaissancesiding.com
Thu Apr 24 10:26:11 CDT 2003
Or at least change the subject line to MACRO DEFINITION or something? Thanks, Bob Gajewski On Thursday, April 24, 2003 11:13 AM, Seth Galitzer [SMTP:sgsax at ksu.edu] wrote: > I really hate to butt in, as this academic discussion as been absolutely > *fascinating*, but I think we're getting into hair-splitting on > sematics. So can we wrap it up, folks? > > Thanks > > Seth > > On Thu, 2003-04-24 at 09:27, Susan Harkins wrote: > > > > > > > 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 > > > > -- > Seth Galitzer sgsax at ksu.edu > Computing Specialist http://puma.agron.ksu.edu/~sgsax > Dept. of Plant Pathology > Kansas State University > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > >