John Bartow
john at winhaven.net
Wed Apr 23 10:56:55 CDT 2003
Andy: Good point! In all the years I used Lotus 123 I never actually "recorded" a macro. I couldn't remember if there was a recording device or not. I always hand coded my macros - which I guess would imply that there is nothing inherently wrong with saying a macro is code. As I recall I used 123 macros to call other procedures. Same with Word Perfect Macros back in my Unix/DOS WP 5.1 days. IMO "Macro" has some(mostly) gray areas in semantics. JB > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Andy Lacey > Sent: Wednesday, April 23, 2003 9:57 AM > To: accessd at databaseadvisors.com > Subject: RE: [AccessD] VBA question > > > FWIW Lotus 123 was one of the earliest (first I used anyway) PC products > to use macros. And yes you could record them but that definitely wasn't > the definition of macro because you could add simple logic such as > goto's or menu statements and they were certainly still macros. It was > just a mini programming language. Excel started the same way, and then > Word. Their programming capability has increased but ok they still use > the word macro. I don't believe you can limit macro to something > recorded and then say anything else is a procedure. What do you get if > you use the record capability then modify the code, say by a single > instruction? What do you have if you enter code through the keyboard > which is the same as what you might have recorded? I can't see that it > works as a differentiator. > > Andy Lacey > http://www.minstersystems.co.uk > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > > Bryan Carbonnell > > Sent: 23 April 2003 10:47 > > To: accessd at databaseadvisors.com > > Subject: Re: [AccessD] VBA question > > > > > > On 22 Apr 2003 at 23:53, William Hindman wrote: > > > > > ...don't agree Bryan ...macro in the Microsoft context has always > > > > OK well how about we agree to disagree? > > > > To me the terms macro is valid and accurate when programming in Word > > or Excel. To you it's not accurate. I personally don't like the > > connotation associated so I try my best not to use it, but that's > > just me. > > > > -- > > Bryan Carbonnell - carbonnb at sympatico.ca > > The man who claims to be the boss in his own home will lie about > > other things as well. _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/a> ccessd > > Website: > > http://www.databaseadvisors.com > > > > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >