|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
RWOP query, forms and securityOkay, before starting a brand new Acces-project, I had a few questions.
Most of them are answered by reading the articles in this newsgroup and the tips on some MVP-sites. So I am this far : I know how to secure the database with the user level security. I know how to disable the shiftkey (and how the enable again). I know how to work with RWOP queries so that users can only change limited fields in limited records of a single table with use of a corresponding form. I only have one question left : I have one table. I want to use RWOP queries and a form to give rights to edit a few fields of the table. But I like to have on the same form other fields from the table that only can be viewed (and not edited) by the user. How can I arrange that ? Since you are disabling the shiftkey and otherwise locking down the
interface, I suggest you set the properties on those controls in form design i.e. set the Locked property to yes. Also consider deploying a MDE of your database. -- Show quoteHide quoteJoan Wild Microsoft Access MVP "BlackKnight" wrote: > Okay, before starting a brand new Acces-project, I had a few questions. > Most of them are answered by reading the articles in this newsgroup and the > tips on some MVP-sites. > So I am this far : > I know how to secure the database with the user level security. > I know how to disable the shiftkey (and how the enable again). > I know how to work with RWOP queries so that users can only change limited > fields in limited records of a single table with use of a corresponding form. > I only have one question left : > I have one table. I want to use RWOP queries and a form to give rights to > edit a few fields of the table. But I like to have on the same form other > fields from the table that only can be viewed (and not edited) by the user. > How can I arrange that ? Thanks for your help.
So, if I understand it the right way, I can use the Locked property on a form to prevent a user of changing certain fields, and if I disable the shiftkey, no user can get to the tables directly. But if that is so, than I can work without the RWOP queries and link the form directly to the table ? Or am I missing something ? What is, for me, the advantage of deploying a MDE instead od a MDB ? Show quoteHide quote "Joan Wild" wrote: > Since you are disabling the shiftkey and otherwise locking down the > interface, I suggest you set the properties on those controls in form design > i.e. set the Locked property to yes. > > Also consider deploying a MDE of your database. > -- > Joan Wild > Microsoft Access MVP > > > "BlackKnight" wrote: > > > Okay, before starting a brand new Acces-project, I had a few questions. > > Most of them are answered by reading the articles in this newsgroup and the > > tips on some MVP-sites. > > So I am this far : > > I know how to secure the database with the user level security. > > I know how to disable the shiftkey (and how the enable again). > > I know how to work with RWOP queries so that users can only change limited > > fields in limited records of a single table with use of a corresponding form. > > I only have one question left : > > I have one table. I want to use RWOP queries and a form to give rights to > > edit a few fields of the table. But I like to have on the same form other > > fields from the table that only can be viewed (and not edited) by the user. > > How can I arrange that ? BlackKnight wrote:
> Thanks for your help. I would still use the RWOP queries. Access security can be broken; you're > So, if I understand it the right way, I can use the Locked property > on a form to prevent a user of changing certain fields, and if I > disable the shiftkey, no user can get to the tables directly. But if > that is so, than I can work without the RWOP queries and link the > form directly to the table ? Or am I missing something ? putting up as many barriers as possible. > What is, for me, the advantage of deploying a MDE instead od a MDB ? Should the users ever get to the db window, you wouldn't want them to be able to change the design of any forms/reports. -- Joan Wild Microsoft Access MVP
Show quote
Hide quote
"Joan Wild" wrote: Thanks for your help !> BlackKnight wrote: > > Thanks for your help. > > So, if I understand it the right way, I can use the Locked property > > on a form to prevent a user of changing certain fields, and if I > > disable the shiftkey, no user can get to the tables directly. But if > > that is so, than I can work without the RWOP queries and link the > > form directly to the table ? Or am I missing something ? > > I would still use the RWOP queries. Access security can be broken; you're > putting up as many barriers as possible. > > > What is, for me, the advantage of deploying a MDE instead od a MDB ? > > Should the users ever get to the db window, you wouldn't want them to be > able to change the design of any forms/reports. > > -- > Joan Wild > Microsoft Access MVP > > >
Secured Database works exactly right on one computer, but on another not quite r
More security questions Access 2003 on wondows XP de-secure problem Is it any way to programmatically store and hide data inside an Access database that it is not shown The database has been placed in a state... Mystery security group setting changes. Unrecognized database format 'C:\Program Files\Microsoft Office\OF Locked by ADMIN or Exclusive Access add tick boxes inside table Locked out of Access |
|||||||||||||||||||||||