How do I make a query in Access to be not-updateable
I want my queries to NOT be updateable. Is there a way I can force that? Thanks.
ASKER
Let me clarify the scenario - I was too vague.
I have a new access user who is going to be working in my database. When he makes a query, I do not want the recordset to be updateable. I don't want him to accidentally change the data in the recordset returned by the query. I know if the queries are complex enough, the recordset is not updateable. Is there something he can do to assure any query he makes produces a non-updateable recordset?
I have a new access user who is going to be working in my database. When he makes a query, I do not want the recordset to be updateable. I don't want him to accidentally change the data in the recordset returned by the query. I know if the queries are complex enough, the recordset is not updateable. Is there something he can do to assure any query he makes produces a non-updateable recordset?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"When he makes a query, I do not want the recordset to be updateable."
The Key word here is "He' ... when 'He' makes the query. aikimark has specified the way to do this; however, that is not going to be bullet proof by any stretch, since anyone opening the query in design view can change that.
So, a more realistic way is to 1) not allow directly 'viewing' (or editing) data view a 'live' query. Instead, you need to create a UI (forms, etc) to work with the data. This way, based on who the Windows user is, you can set a Form's Allow Edits property to Yes/No accordingly.
mx
The Key word here is "He' ... when 'He' makes the query. aikimark has specified the way to do this; however, that is not going to be bullet proof by any stretch, since anyone opening the query in design view can change that.
So, a more realistic way is to 1) not allow directly 'viewing' (or editing) data view a 'live' query. Instead, you need to create a UI (forms, etc) to work with the data. This way, based on who the Windows user is, you can set a Form's Allow Edits property to Yes/No accordingly.
mx
thanks for the points.
to expand on DatabaseMX comment. You would probably be better off by having a test environment with copies of the production tables. It wouldn't matter if the mysterious 'HE' wrote and executed an update query, since it wouldn't touch the production data.
=======
Another way to do this is to create your own front-end query wizard that is only capable of creating a SELECT query.
=======
Another way to do this is to have an invisible form with a timer event that kicks off every minute (or few seconds) and looks at the saved queries for any UPDATE, INSERT, DELETE, or MakeTable queries. The timer event code could hide or delete the querydef.
to expand on DatabaseMX comment. You would probably be better off by having a test environment with copies of the production tables. It wouldn't matter if the mysterious 'HE' wrote and executed an update query, since it wouldn't touch the production data.
=======
Another way to do this is to create your own front-end query wizard that is only capable of creating a SELECT query.
=======
Another way to do this is to have an invisible form with a timer event that kicks off every minute (or few seconds) and looks at the saved queries for any UPDATE, INSERT, DELETE, or MakeTable queries. The timer event code could hide or delete the querydef.
"Another way to do this is to create your own front-end query wizard that is only capable of creating a SELECT query."
How would that prevent this ?
Another way to deal with this is ... A Form that you select a query form say a List box, then use this code to open the query in Read Only mode:
DoCmd.OpenQuery "TheSelectedQueryName", ,acViewNormal,acReadOnly
mx
How would that prevent this ?
Another way to deal with this is ... A Form that you select a query form say a List box, then use this code to open the query in Read Only mode:
DoCmd.OpenQuery "TheSelectedQueryName", ,acViewNormal,acReadOnly
mx
>>How would that prevent this ?
If this is a user, it might mean that the user has a limited number of application forms for doing their work. The other windows might be hidden from the user, including the database window. If the user didn't have access to the MS-Access query wizard, they would be able to create queries using this query-wizard substitute.
If this is a user, it might mean that the user has a limited number of application forms for doing their work. The other windows might be hidden from the user, including the database window. If the user didn't have access to the MS-Access query wizard, they would be able to create queries using this query-wizard substitute.
One of my applications allows users to create their own SELECT queries. The users can name these queries for later use. The user can see all the queries that they created as well as 'system' queries that I created.
But a stock SELECT query is updatable, unless you set the Recordset Type to Snapshot like you suggested ....
mx
mx
ah. The queries can only be used in a read-only setting. The user does not get to see the query results directly.
If I needed to create a querydef from these, I could programmatically make them read-only via property setting. I could also include a read-only table. My favorite trick here is to have a one-row table and add a read-only query of the table, setting the query's RecordsetType property = 2 (snapshot). Then, I can easily add the read only query in the user-defined query's FROM clause to make it read-only.
If I needed to create a querydef from these, I could programmatically make them read-only via property setting. I could also include a read-only table. My favorite trick here is to have a one-row table and add a read-only query of the table, setting the query's RecordsetType property = 2 (snapshot). Then, I can easily add the read only query in the user-defined query's FROM clause to make it read-only.
" I could also include a read-only table."
In Access? How do you do that ?
"The user does not get to see the query results directly."
aka via a form then ?
mx
In Access? How do you do that ?
"The user does not get to see the query results directly."
aka via a form then ?
mx
>>" I could also include a read-only table."
Typo. Should read "I could also include a read-only query."
Good catch, mx. Thanks.
=======
>>aka via a form then
They do see the results in a form, but in a non-updateable control (multi-column Listbox). They can also run a report that is based on their row-selection criterion.
Typo. Should read "I could also include a read-only query."
Good catch, mx. Thanks.
=======
>>aka via a form then
They do see the results in a form, but in a non-updateable control (multi-column Listbox). They can also run a report that is based on their row-selection criterion.
The alternative is explained in the Access Cookbook 1.16 "save my Queries in a table for better programmatic access and security.
Regards
Friedrich