[AccessD] Access 2007 Question

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

Heh.. You want to see what a butcher job the macro recorder does in
Excel.  I mean what it writes does work, but boy it is ugly and tons of
redunant code.

Cheers
Darryl.

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Tuesday, 27 October 2009 3:22 AM
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

"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential,  may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."