User Level Security Securing Modules?

[Ben]

Is it possible to secure modules in a secured db to only allow certain users
to have access to them? I dont want to use a password if possible.

My db is currently locked down with 2 users/groups, and I would like to
prevent access to the vba code as my internal programming security could then
be bypassed. I will be converting this to an MDE once all 'improvements'
have been made. The current version needs to go into 'production' but the
end users know that there will be enhancements made in the days to come.

Thanks for the help
Ben

 

[Keith Wilby]

Is it possible to secure modules in a secured db to only allow certain
users
to have access to them? I dont want to use a password if possible.

My db is currently locked down with 2 users/groups, and I would like to
prevent access to the vba code as my internal programming security could
then
be bypassed. I will be converting this to an MDE once all 'improvements'
have been made. The current version needs to go into 'production' but the
end users know that there will be enhancements made in the days to come.

Why not just supply an mde front end with each release? It's not as if it's
a long process and it will protect your code without passwords.

Keith.
www.keithwilby.com

 

[Ben]

Thanks for your reply.

Your solution would work however, I would require to make many releases.
The reason I do not wish to do that is that the client wishes to create
reports while the users begin entering the data. I could supply the client
with a unlocked version to create the reports and then import them; however,
i feel they would like to create the reports in-line with live data.

any other possibilities? I was once told that earlier versions of access
allowed the securing of the modules.

Thanks again.

 

[Keith Wilby]

Thanks for your reply.

Your solution would work however, I would require to make many releases.
The reason I do not wish to do that is that the client wishes to create
reports while the users begin entering the data. I could supply the
client
with a unlocked version to create the reports and then import them;
however,
i feel they would like to create the reports in-line with live data.

any other possibilities? I was once told that earlier versions of access
allowed the securing of the modules.

If you split the database (and you should IMO for the multi-user
environment) you could then supply users with an mde and the "client" with
an empty app with links to the back end. That way he could create as many
reports as he wishes to which you could then import into the development
copy of your app.

HTH - Keith.
www.keithwilby.com

 

[Ben]

Thanks for the help. Im going to investigate spliting it to either a SQL
server backend or another mdb back end.

 

[Guest]

any other possibilities? I was once told that earlier versions of access

allowed the securing of the modules.

Yes, and if you try you can still include the same security settings,
which prevent you from double clicking on a module and opening
it from the Access Database Window.

But all versions since 2000 have included a bound in VBA
application, which doesn't check or apply the Access permissions.

In the VBA application, you can open modules from the Project window.

So even if you apply Access Security to the modules, all you
have to do is open the VBA window, and then you can open
any module.

(david)

 

[Ben]

Thanks for that information. I did not know that was possible.