[AccessD] Using macros - good thing or bad? Was RE: OTsearchinname attachments in outlook2003

William,

Yes, that's the #1 reason I stopped using them.  You can tuck your code away 
when you make a MDE/ACCDE but the macros are still easy to access.

Access 2007 introduced the Embedded Macro, which solves this problem to a 
large extent.

Regards
Steve


--------------------------------------------------
From: "William Hindman" <wdhindman at dejpolsystems.com>
Sent: Tuesday, February 23, 2010 12:31 PM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Using macros - good thing or bad? Was RE: 
OTsearchinname attachments in outlook2003

> ...isn't security also a major issue with macros?
>
> William
>
> --------------------------------------------------
> From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
> Sent: Monday, February 22, 2010 5:31 PM
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Using macros - good thing or bad? Was RE: OT
> searchinname attachments in outlook2003
>
>> 1. Error handling.
>> Enough said.
>>
>> 2.  Simplicity.
>> There are many things which I need to do in code that  can't be done in
>> macros, I don;t want
>> to look in one place for half of my application and somewhere else for 
>> the
>> other half - so I do
>> it all in code.
>>
>> 3.  Maintainability.
>> It's much easier to search through and edit code modules than it is to
>> search through macros
>> and the actions in them.