[AccessD] Using macros - good thing or bad?

Collins, Darryl Darryl.Collins at anz.com
Thu Feb 25 19:01:21 CST 2010


Hehehe... Yeah... 6 months in and I am *still* waiting to get
permissions to use SQL Server.  Of course I made the right decision by
using an Access BE on the LAN, which I got up and running on day 1.  It
is a bit sluggish compared to SQL server, but hey, at least it is
something....

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Friday, 26 February 2010 4:17 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Using macros - good thing or bad?

Very Interesting.
However, mention VBA to anyone in corporate IT, and they look at you
like a vampire would when seeing sunlight.
http://www1.phillyburbs.com/vamp/defenses.shtml

Of course, if anyone here has had any recent experience with large
corporate IT departments,  you would say they all BEHAVE like vampires.
They'll suck the blood out of anyone who encroaches upon their  turf.



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




More information about the AccessD mailing list