How to protect a query

[Guest]

Dear all,

How to protect a query with a password, I mean protect only the queries -

Is there any way?

Access 2003 with Windows XP

Thanks

 

[Guest]

Protect them from what? Being used or being modified?

Protect from use requires user level security and setting the RunPermissions
with something like WITH OWNERACCESS OPTION in the sql.

You could protect them from being altered by putting the SQL in modules and
then creating an MDE file.

You could hide the queries by naming the starting with Usys_

These methods require a lot of effort. I find that a 2"x4" strategicly
placed upside a user's hear is effective in stopping them from messing with
things.

 

[Guest]

Dear,
Yes the intention is only to stop the modification - based on the created
queries I have made reports, so now users just execute the reports instead of
looking and modifying the query.
is there any way to protect only queries?

Please advise

 

[Joan Wild]

Open the query in SQL view and copy the SQL statement. close the query and
open your report in design view. Paste the SQL statement in place of the
query for the recordsource.

You can now delete the query, provided it isn't used elsewhere.

Then you can create a MDE from your MDB and users won't be able to modify
the report.

Be sure to keep a copy of the MDB in case you need to make further changes.

 

[Pat Hartman\(MVP\)]

You would need to implement Access security. You would give access to
everything to whoever will be responsible for maintaining the app and
limited access to everyone else. You should not assign security directly to
individuals. Assign individuals to groups and assign security to groups to
save yourself a lot of maintenance. The users will need to login when the
database opens.

IMPORTANT - before starting anything this major, make sure that you have
several backups in a safe place. You also need to read the Security FAQ
from the MSDN library and follow its directions EXACTLY.

If you don't want to get involved with Access security, use the suggestion
to hide the queries by changing their names. If you have A2003, turn on the
NameAutoCorrect property before you make the change. Test everything. Then
turn off NameAutoCorrect again. A2K and AXP also support NameAutoCorrect
but less reliably. Make sure you have the latest service packs installed.

 

[Guest]

Much smarter than my idea of putting the SQL in modules!