Prohibiting Changes to a Database Design

I know I ran across the solution to this before, but I'm drawing a blank
now. I designed a database that is used by one person. He keeps trying
to make changes to the design and then I get called in to fix the
problem. In the past he has been caught intentionally changing my work,
then complaining to management that the database didn't work.
Fortunately, I had back-up copies hidden on the computer that he was
unaware of. I want to protect that database so that only the data can be
changed/entered and no changes can be made to the design of the forms,
tables, queries reports, etc. Can this be done with a password and
without changing the database to an "mde" file.

Any help will be much appreciated.

Regards,


Mike

See the Access Help about "Securing a Database". Making it an MDE is a
better way to protect form/report/module design, but does not protect table
and query access.

Mike Storr
www.veraccess.com


"Mike Farmer" <farmer.m@comcast.net> wrote in message
news:6OH2c.132677$Xp.558524@attbi_s54...[color=blue]
> I know I ran across the solution to this before, but I'm drawing a blank
> now. I designed a database that is used by one person. He keeps trying
> to make changes to the design and then I get called in to fix the
> problem. In the past he has been caught intentionally changing my work,
> then complaining to management that the database didn't work.
> Fortunately, I had back-up copies hidden on the computer that he was
> unaware of. I want to protect that database so that only the data can be
> changed/entered and no changes can be made to the design of the forms,
> tables, queries reports, etc. Can this be done with a password and
> without changing the database to an "mde" file.
>
> Any help will be much appreciated.
>
> Regards,
>
>
> Mike
>[/color]

Don't just rely on Help to secure a database. It's easy to miss something
and have it so secure that even you can't log in, or so insecure that anyone
can.

Download the Security FAQ from http://www.microsoft.com/downloads and give
it a good study. It's not trivial, and it can be broken, but likely will
frustrate the guy who just feels he "can do it better" and ends up breaking
the DB.

Larry Linson
Microsoft Access MVP
"Mike Farmer" <farmer.m@comcast.net> wrote in message
news:6OH2c.132677$Xp.558524@attbi_s54...[color=blue]
> I know I ran across the solution to this before, but I'm drawing a blank
> now. I designed a database that is used by one person. He keeps trying
> to make changes to the design and then I get called in to fix the
> problem. In the past he has been caught intentionally changing my work,
> then complaining to management that the database didn't work.
> Fortunately, I had back-up copies hidden on the computer that he was
> unaware of. I want to protect that database so that only the data can be
> changed/entered and no changes can be made to the design of the forms,
> tables, queries reports, etc. Can this be done with a password and
> without changing the database to an "mde" file.
>
> Any help will be much appreciated.
>
> Regards,
>
>
> Mike
>[/color]