Disable changes to queries?

[Cosmos75]

Is theere anyway to not allows any changes to be made to the queries in a database? I have a split database and I"ve made the Front End into an MDE but the user could still change the queries?!?!


(Access 97 for this question)

 

[RichMorrison]

First, I don't believe the users can "change" a query in a front end that has been converted to an MDE.

Second, you can use internal permission settings so that members of the group Users can not modify the design of queries.

RichM

 

[Cosmos75]

First, I don't believe the users can "change" a query in a front end that has been converted to an MDE.

Second, you can use internal permission settings so that members of the group Users can not modify the design of queries.

RichM

I just tried it and I was able to change a query...


The only security I have on the db is a password. I entered the password and held down the shift key to see the database window and viola, I was able to see the query in design view AND change it!!

Am afriad to set user permissions using Access security as it will run an someone else's network and I've never used it before.

 

[Pat Hartman]

I don't blame you for being afraid but the only way to prevent the user from modifying queries, tables, and macros is to use Access security.

Make sure you read the FAQ published by Microsoft VERY CAREFULLY before proceeding and searching the archives here will produce any number of horror stories.

 

[Fizzio]

A simpler way would be to disable the shift key so that the end user could not use that shortcut to show the database window. ColinEssex/Hayley have both posted a good example of how to do this.

 

[RichMorrison]

You wrote
<<
I just tried it and I was able to change a query...
>>

Yup, memory failure at this end

Meanwhile, if you go to Tools/Security/User and Group Permissions and select permissions by Group you can remove "Modify Design" and "Administer" permissions from the group Users.

You can and should do this for all objects in the data base.

If you do this when you are first creating a database and you remove Modify/Administer permission for new objects, then you don't have to do it one object at a time.

I have been doing this since Acc97 was introduced and have experienced no problems.

RichM

 

[jfgambit]

Cos:

I created a MDE file, disabled the "Shift on Enter" and F11 functions to keep users out of the front-end and have not had any problems with them chaging queries (of course we are not dealing with rocket scientists here). I have a db that after creating a MDE will allow you to select the database and disable or enable the Shift and F11 functions. Let me know if you want it and I'll post it.

It might help with you situation...

 

[Cosmos75]

jfgambit,

I would be interested in seeing how you've disabled the Shift key after creating the MDE.

Pat,

I will do a little more research on using Access Security. I think I've somewhere where you can create an individual .mdw file for a particular database and not have to touch the system.mdw.

Security probably won't be a problem with the database but I figure it's my fiduciary responsibility to ensure that it won't become a problem.

On another topic but somewhat related:
I am wondering, is it ethical to hide the queries if I just give it to someone "as-is" and not provide any support? I mean, it's developed in Access 97 but what if the upgrade to Access 2000 or XP? I plan to leave the tables as an .mdb file as it's their data but I don't want to leave the ability for someone to reverse engineer the query/forms/report design? Is that just me being mean?

 

[jfgambit]

Cos:

Here's the DB...

I am wondering, is it ethical to hide the queries if I just give it to someone "as-is" and not provide any support?

What kind of agreement did you sign with the Client? Are they entitled to a complete db with code descriptions and details, or did they provide the data and say "go for it." If is the later of the two then I suppose the code belongs to you to lock up as you see fit, if it's not then you might not need any of these additonal secuirity features. Just amke sure to get some kind of "You break it, you pay for a fix" addendum to the contract.

HTH