[AccessD] Using macros - good thing or bad?

  I haven't looked at 2010 yet (install still sitting on the desktop) and
while macro did make progress in 2007, they are still a far cry from VBA.

  And macros still can't call anything external (Win API, DLLs, COMs, etc).

  Microsoft has a long way to go with they want to move away from VBA and
the security of macros.  At least from my view point anyway.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel
Sent: Tuesday, February 23, 2010 1:39 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Using macros - good thing or bad?

Ken,

--------------------------------------------------
From: "Kenneth Ismert" <kismert at gmail.com>
Sent: Wednesday, February 24, 2010 5:16 AM
To: <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Using macros - good thing or bad?

> This means they still don't support variables.

Access 2007 introduced TempVars.  These are very cool critters.  They can be

created in macros or in VBA, and once created can be used similar to global 
variables or local variables in macros or VBA, but also can be used for 
example in query criteria, and in calculated fields, and then Control Source

expressions of form or report controls.

Access 2010 goes a step further.  This is still not to the extent that you 
would no doubt desire, but it's still worth noting that "don't support 
variables" isn't quite true.

Regards
Steve 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com