Protecting queries

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?!

Both of those positions are very complex (at least if you wish to survive).


"Granny Spitz via AccessMonster.com" u26473@uwe wrote in message
news:698b05470ce87@uwe...
C Tate wrote:
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.

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.

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

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...eries/200611/1

"C Tate" wrote in message
...
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?!

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.


--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

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.
"Rick Brandt" wrote in message
et...
"C Tate" wrote in message
...
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?!

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.


--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com