[AccessD] Macro Example

In Word, there are Document New, Open and Close event procedure hooks that 
are not invoked by a user but by one who writes code.  As far as I know, a 
user can only avoid the code by disabling macros or placing a break in the 
code window and ending execution, and that is only possible if the document 
is not locked.  I believe code must be written or pasted into these hooks 
and cannot be recorded directly into them.  Note also that Access 97 has the 
facility to convert Access macros to code, complete with error handler.  
Excel and Word also have a forms/controls interface and although the 
procedures, both functions and subroutines, are commonly called macros, this 
deprecates the reality.  I have written procedures in Word and Excel that 
have updated a database.  A Word form using code with a reference to DAO or 
ADO is as capable as any unbound Access form.  Then again, there are many 
who consider Access a toy and VBA in code little more than macros.  Maybe 
when Access becomes fully object oriented and better supports collaborative 
development???  Access macros are unique in comparison with the rest of the 
Office suite.

Hen






>From: "John W. Colby" <jcolby at colbyconsulting.com>
>Reply-To: accessd at databaseadvisors.com
>To: <accessd at databaseadvisors.com>
>Subject: RE: [AccessD] Macro Example
>Date: Thu, 24 Apr 2003 17:42:24 -0400
>
>If I may chime in...
>
>Macros in Excel CREATE visual basic code.  A macro recorder (in the olden
>days) was a recording of the keystrokes and mouse clicks that the user
>entered.  Excel still works that way, but the "macro" is no longer just the
>recorded keystrokes, but rather a VB program that represents the results of
>those mouse clicks and keystrokes.  Thus a macro in Excel isn't truly a
>macro in the original sense, but rather a true VB program that emulates the
>original intent.
>
>John W. Colby
>Colby Consulting
>www.ColbyConsulting.com
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
>rusty.hammond at cpiqpc.com
>Sent: Thursday, April 24, 2003 2:31 PM
>To: accessd at databaseadvisors.com
>Subject: RE: [AccessD] Macro Example
>
>
>If I may chime in.  I think it was SusanH that posted the definition of a
>macro according to pcwebopedia that stated "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."
>I think Microsoft has taken the sophisticated macro to an extreme with Word
>and Excel macros, nonetheless Microsoft obviously still considers them a
>macro since you get to them by going to Tools/Macros.
>
>If I were writing a book about Word or Excel, I would refer to these
>procedures as macros.  If I were writing a book about Access, I would point
>out the difference betweeen macros and modules.  If I were writing a book
>about all three, I would point out the modules in Access use the same VBA 
>as
>Word and Excel macros.  It all depends on what application you're talking
>about and that particular applications' use of the technology.
>
>just my 2 cents.
>
>RustyH



_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*   
http://join.msn.com/?page=features/junkmail