Gustav Brock
Gustav at cactus.dk
Mon Oct 26 11:55:30 CDT 2009
Hi Martin Ouch, it certainly does. Looks like Access is approaching FileMaker. I'm out. /gustav >>> mwp.reid at qub.ac.uk 26-10-2009 17:35 >>> This gives you a good idea of where macros are going http://blogs.msdn.com/access/archive/2009/07/28/meet-the-access-2010-macro-designer.aspx Martin Martin WP Reid Information Services The Library at Queen's Tel : 02890976174 Email : mwp.reid at qub.ac.uk ________________________________________ From: accessd-bounces at databaseadvisors.com [accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust [cfoust at infostatsystems.com] Sent: 26 October 2009 16:22 To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access 2007 Question Access certainly used to have a wizard for converting macros to code, but it didn't do a very good job, since it created obsolete code in the process. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Sunday, October 25, 2009 1:39 PM To: Access Developers discussion and problem solving Subject: [AccessD] Access 2007 Question I have downloaded and built all the Access 2007 template apps. Every single one of them does its magic with macros not with VBA. This begs some questions: 1. Does this indicate that developers are no longer welcome in the Access community? How are we to read this, when even Northwind has been translated to macros from VBA code? 2. Is there a wizard that converts a macro to VBA code? Or should I just cut and paste the macro in question to the code window and then attempt to translate it to VBA code? 3. Should we Access developers regard this as the definitive signal to move to Visual Studio or some other dev platform? (Just about the only thing that keeps me on Windows is Access; take away that and you may as well call me an Ubuntu boy.) Arthur