Lock the code w/o locking out the user???

  • Thread starter Thread starter Timothy
  • Start date Start date
T

Timothy

Hello,
Does anyone know of a way to keep users on a user level
security system from viewing the code behind events
without password protecting the project??? I have a
database where I allow users to modify the database by
deleting tables and forms if needed, but I dont want them
to have access to the Code. I have found out that if a
password is placed on the project in the VB then the user
cant delete the forms or reports. Anyone have an idea???

Thanks
Timothy
 
Does anyone know of a way to keep users on a user level
security system from viewing the code behind events
without password protecting the project??? I have a
database where I allow users to modify the database by
deleting tables and forms if needed, but I dont want them
to have access to the Code. I have found out that if a
password is placed on the project in the VB then the user
cant delete the forms or reports. Anyone have an idea???
Click to expand...

?????

What are users doing deleting forms and reports? Are they adding new objects,
also? If users are going to have such unlimited access to modifying the
database, then you will not be able to protect your code - if not, then you
could consider creating an MDE file to distribute (this strips the readable
code, leaving only the compiled version of the code), keeping the original MDB
in a safe place to allow future changes.
 
As Bruce said, this sounds like an odd situation!

Could you move the bulk of the code from your current database (db1), into a
new, external database (db2)? Then change db1 to call procedures in db2.
Establish a reference from db1 to db2 (Tools:References), and lock the
project in db2. Then, they *can* still look at your code in db1, but all
they see is calls to procedures in db2 - and they can't view the code in
db2.

But why do you want to do this? If the code behind the forms is so
confidential/complicated/valuable or whatever, why do you let the users
delete it?

HTH,
TC
 
The users really wont be looking at the code, mostly are
just keeping up with using the database. They need access
to delete tables and reports becuase it will create a
report for specific functions, and usually its a one time
use. SO they need to be able to delete objects, but I
dont want them or anyone who knowns how to really use
access to see the code. They have to have modify
privilleges in order to use it. just dont want them to
mess with a years worth of work.

Timothy
 
The users really wont be looking at the code, mostly are
just keeping up with using the database. They need access
to delete tables and reports becuase it will create a
report for specific functions, and usually its a one time
use. SO they need to be able to delete objects, but I
dont want them or anyone who knowns how to really use
access to see the code. They have to have modify
privilleges in order to use it. just dont want them to
mess with a years worth of work.
Click to expand...

Have you looked into Access User-Level Security? If you haven't, I recommend
that you obtain the Access Security FAQ, available at:

http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

If you think that this is something that you might want to tackle, then post
related questions to the Security newsgroup (microsoft.public.access.security)
for a better availability of experts in that subject.

:-)
 
Back
Top