John W. Colby
jcolby at ColbyConsulting.com
Fri Apr 25 07:18:24 CDT 2003
>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 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Drew Wutka Sent: Friday, April 25, 2003 2:42 AM To: 'accessd at databaseadvisors.com' Subject: RE: [AccessD] Macros Actually, that is the core of this discussion. Because Access Macros are just as powerful as VBA, since they have a RunCode command. Sure, it's moronic to write code, and run them all 'through' macros, but it definitely means that macros in Access can be more powerful then they appear. So the real difference, IMHO, is that a macro is a term used to describe a simple user automation interface, regardless of what they look like inside. Macros in general are 'simplistic' to write....for a common user. However, in Excel and Word macros can be built completely with code, never using the recorder, and since the macro IS VBA, they blend into VBA more fluidly then in Access. You still have strictly VBA capabilities in Excel and Word (events, forms, etc.) so macros in Excel/Word do not completely embody VBA. The blurry distinction is just 'crisper' in Access since the macro design window is a stepped command process, versus a recorder. Quite frankly I think they should have a macro recorder in VBA, but I think the issue with dealing with db data makes that a very daunting task. Drew -----Original Message----- From: Mwp.Reid at Queens-Belfast.AC.UK [mailto:Mwp.Reid at Queens-Belfast.AC.UK] Sent: Thursday, April 24, 2003 12:22 PM To: accessd at databaseadvisors.com Subject: [AccessD] Macros An Access Macro is not the same as a macro in Word or Excel or Powerpoint. In access its more recording an action. In WOrd and Excel and Powerpoint its writing code - VBA code. Thus its a good way to learn the model for those apps. Now how they actually work in Access, I think all they do is actuallyc arry out a menu command. They dont have the power of a Word Macro for example. Teh one I posted opens a document located in the file system. If I had wanted to I could have then applied styles etc to that doc and then the appropriate code would be created. Dont think an Access Macro will do that. Martin _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com ----------------------------------------------------- eMailBoss puts you in command of your email. Get your copy today at http://www.eMailBoss.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 3240 bytes Desc: not available URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030425/a14ad547/attachment-0001.bin>