Opening query as read-only

[mscertified]

I'm trying to make it more difficult for users to accidentally delete table
records. This database formerly exposed the dataase window and since there
are lots of queries the users run, I created a form containing a drop-down
which lists all the queries. The users selects the query and clicks a button,
I then open the query with read-only. It works ok, the user cannot change
anything or delete rows. However, if the user sorts a column then clicks the
X, a prompt appears 'do you want to save changes to the design of query
xxxx'. Why? and what would happen if they clicked 'yes'. Seems odd that this
prompt would appear when I opened the query as read-only.

 

[Rick Brandt]

I'm trying to make it more difficult for users to accidentally delete
table records. This database formerly exposed the dataase window and
since there are lots of queries the users run, I created a form
containing a drop-down which lists all the queries. The users selects
the query and clicks a button, I then open the query with read-only.
It works ok, the user cannot change anything or delete rows. However,
if the user sorts a column then clicks the X, a prompt appears 'do
you want to save changes to the design of query xxxx'. Why? and what
would happen if they clicked 'yes'. Seems odd that this prompt would
appear when I opened the query as read-only.

Opening a query as read only ONLY affects data changes, not design changes.

Users should not have direct access to either tables nor queries. Give them
forms instead.

 

[mscertified]

That's exactly whay I am doing - giving them access to queries via a form. I
don't have time to give them a separate form for every query as there are
hundreds of them.