|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Password protectionI know there is a way to password protect an entire form, but is there any
way that I can password protect just one particular field [datereceived] in a form frmNewfile, so that when an attempt is made to enter or change the data in [datereceived], the user is prompted for a password before the entry can be made? Best I can figure is to put all such fields on one form and password protect the form, but I would rather not do it this way if possible. Thanks. I don't know of any way to do that offhand, but can think of a round about
way to do it. I am sure there are others on here that can think of better ways to do this. Field getfocus () if vrbPassword = false then 'the password has not been entered yet open password_entry form end if form password_entry () 'once password has been entered check to ensure password is correct if correct then set vrbPassword = true end if Troy Show quoteHide quote "RickJ" wrote: > I know there is a way to password protect an entire form, but is there any > way that I can password protect just one particular field [datereceived] in a > form frmNewfile, so that when an attempt is made to enter or change the data > in [datereceived], the user is prompted for a password before the entry can > be made? > > Best I can figure is to put all such fields on one form and password protect > the form, but I would rather not do it this way if possible. > > Thanks. Personally, I'd hate to have password prompts pop up every time I wanted to
make entries in a field. A better idea is to enable or disable that field based on who is logged on. Don't make your higher level employees type in secret passwords every time they try to do something important. Ask for a userid and password once when you open the database and then set all your access based on that one login. Also, using the method you mention, what would prevent the user from simply opening the table, or query and changing the field? Or, what would create the user from creating their own simple form and including that date field? Or, what would prevent them from reading your code and seeing the password there? Lots more to security than just adding a pop-up prompt and asking for a password. -- Show quoteHide quoteRick B "RickJ" <Ri***@discussions.microsoft.com> wrote in message news:D3873092-0570-4181-B212-A1E4507220A7@microsoft.com... >I know there is a way to password protect an entire form, but is there any > way that I can password protect just one particular field [datereceived] > in a > form frmNewfile, so that when an attempt is made to enter or change the > data > in [datereceived], the user is prompted for a password before the entry > can > be made? > > Best I can figure is to put all such fields on one form and password > protect > the form, but I would rather not do it this way if possible. > > Thanks.
Credit Card Masking
Security without signon Creating a secure database on a network Basing Object Permissions on Ownership Access Tools Menu Disabled Access security best practice - Stupid question(s) #2 Access Security Invalid page fault in module RPCRT4.dll Prompting Users for a new password Multi-user database with common front-end |
|||||||||||||||||||||||