Locking Queries, Forms and Reports

[Guest]

I have created a number of Forms, Reports and Queries for my client. Is
there a way of locking these items so that normal users can not modify them?
I don't want to lock the database just the above mentioned.

Thanks

 

[Larry Daugherty]

Convert the Front End to an MDE. If the user site actually needs the
MDB, ship it to the manager or administrator concerned. If ANYONE
gets a copy of the MDB then the fox is loose in the henhouse. Where I
have ongoing work with a client I make all changes on a copy of the
MDB that has never left my custody. I absolutely, positively and very
sincerely refuse to be responsible for code that may have been altered
by someone else since I last had it.

HTH

 

[Guest]

Larry, that is good advise but I am one of those kind of guys that doesn't
like to quess. I suppose that means no there is not a way of locking these
things.

Thanks

 

[Larry Linson]

Larry, that is good advise but I am one of those kind of guys that doesn't
like to quess. I suppose that means no there is not a way of locking these
things.

You can get the Access Security FAQ and apply security -- you can grant
permissions to a group, and assign all users to that group. Don't give the
users any design view permissions on the objects you want to protect. I
suppose you could remove Admin from the Admins group, and everyone could
continue to just open and use... there's nothing that says the default login
name "Admin" actually has to have any design view permissions.

Larry Linson
Microsoft Access MVP

 

[Guest]

I am surprised and disappointed that there is not a way to lock individual
queries, forms and reports from being modified with out requiring the whole
database from coming under a password protection. You can protect individual
documents or spreadsheets. A small business does not want to use passwords
but there you don't want your reports, forms or queries changed.

Thanks

 

[Larry Daugherty]

The way you asked the question may have gotten you the wrong answers
to your real question. It sounded like you didn't want people messing
with the data elements. By converting your application to an MDE file
you'll protect the design of all of the things you mentioned without
having to implement security.

First of all, your application should already be split into a Front
end (with all of the things you're concerned about) and a Back End
which will have just the tables. You should do that as a matter of
course for every application. That solves a host of issues regarding
maintaining an application that has live data.

Convert just the front end into an MDE. When that is done, be sure to
save the MDB un a secure area and then distribute the Front End MDE
with the Back End MDB.for use. The MDE format has all of the source
code removed and can no longer be modified.

Future design changes will be made to a copy of the MDB you've saved
and you Alco convert a copy to MDE format before releasing it. You
can grab a copy of the production Back End so you'll have real data
for testing. You'll only have the hassles of managing the data in
cases where you've had to change the table designs.

Access Help will guide you in splitting your application. Same for
making an MDE.

HTH