Protecting queries

  • Thread starter Thread starter C Tate
  • Start date Start date
C

C Tate

Is it possible to protect my queries from alteration? I don't want to create
an MDE file because I still want them to be able to access the database
window to run reports. I also don't want users to go through complicated
logon procedures. Maybe I'm asking the earth?!
 
C said:
Is it possible to protect my queries from alteration? I don't want to create
an MDE file because I still want them to be able to access the database
window to run reports.
Click to expand...

Don't worry. An MDE won't protect the tables, queries or macros in any way.
The only ways to protect the queries are to either apply User level security
or avoid saving queries and just use SQL in the VBA code in modules.
I also don't want users to go through complicated
logon procedures.
Click to expand...

If double-clicking a shortcut, being prompted with the last user name to sign
in (usually their own) and having to type the password are too complicated
for your users maybe they should find a less complex occupation. There're
always positions open for paratroopers and lion tamers. No computer
experience required. <g>
 
John said:
Both of those positions are very complex (at least if you wish to survive).
Click to expand...

John, I'm sure you've met people who were in very complex positions they
managed admirably, but when it comes to computers they're "all thumbs." They
think their own job is manageable but computers are difficult or too complex.
Working with computers seems to be either a different mindset or a different
skillset altogether, and inability to work with computers is no reflection on
their overall capabilities.
 
C Tate said:
Is it possible to protect my queries from alteration? I don't want to create
an MDE file because I still want them to be able to access the database window
to run reports. I also don't want users to go through complicated logon
procedures. Maybe I'm asking the earth?!
Click to expand...

You have a few incorrect assumptions.

An MDE does not restrict access to the db window.

An MDE does not prevent design changes to queries and tables. Only to code
based objects.

Depending on how many queries you have you could have a code routine that
changes them all back to your current design in case anyone messes with them.

Depending on the sophistication of your users you could hide them or name them
with USys as a prefix which would cause Access to hide them as system objects.
 
Thanks for clarifying that Rick. Both options sound interesting. Are there
any sites that give sample code for changing queries back to the original
design? Also, if I give my queries the usys prefix how do I see them myself
if I wish to view/amend? Sorry I'm so ignorant; I'm quite new to Access.
 
Back
Top