Disable macros?

[Billy R. Moon]

Has anyone ever come up with a way to disable macro creation within MS
Access? Not just on a project level, but to prevent macros from being
created and/or ran on a particular PC or by a particular user.

It doesn't really matter whether macros can still be ran, just need to
prevent certain users from being able to create them. (Or vice versa, if
they can create macros but not run them, that accomplishes the same thing).
The kicker is that there is VBA code in some of our apps that will still
need to run.

I'm asking in particular about Access XP, but I'd love to hear from anyone
that's been able to pull it off in any version.

[Bradley]

Billy R. Moon wrote:

Has anyone ever come up with a way to disable macro creation within MS
Access? Not just on a project level, but to prevent macros from being
created and/or ran on a particular PC or by a particular user.

It doesn't really matter whether macros can still be ran, just need to
prevent certain users from being able to create them. (Or vice versa,
if they can create macros but not run them, that accomplishes the
same thing). The kicker is that there is VBA code in some of our apps
that will still need to run.

I'm asking in particular about Access XP, but I'd love to hear from
anyone that's been able to pull it off in any version.

Distribute an .MDE version of your database?
--
regards,

Bradley

[Billy R. Moon]

We need to disable the capability for ALL databases, not just for a
particular project. The idea is to prevent non-programmers from being able
to create 'applications' using macros that will be difficult to maintain.

"Bradley" <br*****@REMOVETHIScomcen.com.au> wrote in message
news:jb****************@news-server.bigpond.net.au...

Billy R. Moon wrote:

Has anyone ever come up with a way to disable macro creation within MS
Access? Not just on a project level, but to prevent macros from being
created and/or ran on a particular PC or by a particular user.

It doesn't really matter whether macros can still be ran, just need to
prevent certain users from being able to create them. (Or vice versa,
if they can create macros but not run them, that accomplishes the
same thing). The kicker is that there is VBA code in some of our apps
that will still need to run.

I'm asking in particular about Access XP, but I'd love to hear from
anyone that's been able to pull it off in any version.

Distribute an .MDE version of your database?
--
regards,

Bradley