[AccessD] Access 2007 Question

Rocky Smolin rockysmolin at bchacc.com
Mon Oct 26 15:25:56 CDT 2009


All good reasons.  So now I'm wondering if there isn't a place for both -
that if you're adept at writing those macros if they wouldn't be quicker for
the things that you CAN do with macros than generating code.

Rocky
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Monday, October 26, 2009 1:12 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 Question


 Error handling, the ability to call the windows API, etc.   Overall
flexibility in coding.

Jim.



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Monday, October 26, 2009 1:01 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 Question

In general, why is there a preference for VBA over macros?  I can see where
VBA might have more flexibility but for repetitive cookie cutter tasks
aren't macros quite effective?  

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Martin Reid
Sent: Monday, October 26, 2009 9:36 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access 2007 Question

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-d
esigner.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
--

--
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

--
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




More information about the AccessD mailing list