[AccessD] Macros

As I mentioned before, you can have user forms and controls in Excel and 
Word.  From the Excel help:

"The controls available on the Control Toolbox are known as ActiveX 
controls. ActiveX controls are similar to controls you find in programming 
languages such as Visual Basic, and they are the same controls you can add 
to custom forms you create by using the Visual Basic Editor. When you add an 
ActiveX control to a worksheet, you write a macro code that is stored with 
the control itself, not just assigned to run when you click the control."

And you can set a reference to various libraries including DAO or ADO, 
create connections to any kind of database you can in Access and run any 
kind of queries or procedures that can be coded.  Microsoft seems to have 
extended the word 'macro' when used in Excel and Word to mean VBA.  And I'll 
repeat what I said in the Marco Example thread...  Word Documents have event 
procedures that need code written (or pasted) rather than recorded.  For 
example, the Open, New and Close document events.  Microsoft calls any code 
in these events macros.

It would be a misnomer to call such procedures scripts because languages 
like VB Script have a shadow of the capabilities of VBA accessed through 
Word and Excel 'macros' via their IDE.

Hen




>From: Drew Wutka <DWUTKA at marlow.com>
>Reply-To: accessd at databaseadvisors.com
>To: "'accessd at databaseadvisors.com'" <accessd at databaseadvisors.com>
>Subject: RE: [AccessD] Macros
>Date: Fri, 25 Apr 2003 12:20:31 -0500
>
>Hey, no, that's not what I said, and least not what I meant! <grin>  I 
>meant
>that the Macro is just an 'interface' to what is done in the background.  
>In
>Excel/Word, the macro is what runs a VBA procedure.  The VBA procedure IS
>VBA, but the Macro is just the process that kick starts it.  In Access, you
>have stepped macros, but those steps can also run code, so they are just as
>powerful as an EXCEL/WORD MACRO.  Macros (in either platform) can be
>triggered by events...they have to be run by the user.  (Well, you can 
>'run'
>a macro from code within an event...but you know what I mean).
>
>I was not saying that macros are as powerful as VBA.
>
>Drew
>
>-----Original Message-----
>From: John W. Colby [mailto:jcolby at colbyconsulting.com]
>Sent: Friday, April 25, 2003 7:57 AM
>To: accessd at databaseadvisors.com
>Subject: RE: [AccessD] Macros
>
>
>Yes, but now you are programming in VB.  The argument was that Macros were
>"just as powerful as VB".  If you have to use VB to do something that 
>Macros
>can't accomplish, then the argument is proven false.
>
>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 Don Elliker
>Sent: Friday, April 25, 2003 8:51 AM
>To: accessd at databaseadvisors.com
>Subject: RE: [AccessD] Macros
>
>
>
>Could it not be called in a function and the function called from the 
>macro?
>_d
>
>
>
>
>
>"Things are only free to the extent that you don't pay for them."
>
> >From: "Jim Dettman"
> >Reply-To: accessd at databaseadvisors.com
> >To:
> >Subject: RE: [AccessD] Macros
> >Date: Fri, 25 Apr 2003 08:23:56 -0400
> >
> >The other major distinction is that there is no way to call an API 
>function
>
> >from a macro.
> >
> >Jim Dettman
> >President,
> >Online Computer Services of WNY, Inc.
> >(315) 699-3443
> >jimdettman at earthlink.net
> >
> > > -----Original Message-----
> > > From: accessd-bounces at databaseadvisors.com
> > > [mailto:accessd-bounces at databaseadvisors.com]
> > > Sent: Friday, April 25, 2003 8:18 AM
> > > To: accessd at databaseadvisors.com
> > > Subject: RE: [AccessD] Macros
> > >
> > > >Because Access Macros are just as powerful as VBA, since they have a
> > > RunCode command.
> > >
> > > Nope, gotta disagree there Drew. No developer worth his salt will 
>touch
> > > macros for development in Access for the simple reason that errors
>cannot
> > > be handled. In a runtime errors will dump you to the dos prompt.
> > > Furthermore there is no facility for getting at the object model. 
>Macros
>
> > > are an extremely simplistic "programming language" for power users, 
>and
>do
> > > not compare in any way to VB.
> > >
> > > John W. Colby
> > > Colby Consulting
> > > www.ColbyConsulting.com


_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online  
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963