Security For Queries

R

RI

-----Original Message-----
do?

And yet it's desireable for them to update via a form? Either you want
users to be able to update the data or not. Could you elaborate some more?


Thanks For Helping------------ I don't want anyone to
update via the queries themselves. For example ,In a query
that counts the number of times a demo copy opens and then
limits people to opening the database a certain number of
times, I can't have people resetting the counter. The
counter would not be visible by form, but if people were
able to change data directly in the query they would
bypass the security.

I have secured my tables and access them with RWOP
queries. I should only have to give "read data" permision
to the runtime workgroup in order to use forms with these
queries. It is true that when I do this---1.The forms
based on these queries open.--- and 2. The queries are not
updateable when then are opened directly(which is good).
The problem is that the queries and forms based on
them become unupdateable. If I add "update,add,delete
data" to the runtime workgroup permissions, then---1. The
forms work wee and are updateable but the runtime
workgroup has the ability to chang data when they open the
queries directly. What is the fix and why are there no
permission settings for modules. thank you
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top