Record lock and password access

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello everyone,

On my form I have it set to open to a new record for users to input there
comments. However, I do not want users to go back to view previous record
because of sensitive information. I would like to hide the record selector at
the bottom of the form but I create a command button so when clicked, will
require a password and if the password is correct will make the record
selector visible. If so, please simplify explantion.

Thank you!!
 
Just set your form to "data entry" and they will not be able to see previous
entries.

Your button could turn off the data entry property, or you could have two
different forms - one for folks who can see and modify history, and one for
folks who can't.

Or - best solution - run code when you open the form to set the property.
If the user should be able to make changes, then set the data entry property
to false, if not, then set it to true.
 
Hi Rick,

I'm sorry, I mention Navigation Buttons not Record Selector. Not sure if
that makes a difference in your response but I would still like to try the
way I mentioned if possible. I am still a novice at Access so please simplify
response.

Thanks!!
 
Not sure if you can turn off the record navigators in code, but I would
assume that is one of the settings. You could also prompt the user for a
password and then check it, but that is horribly unsecure. The user could
look at your code and see the password, or they could simply ignore your
form and open the table directly.

You should step back and use proper security techniques - don't take
shortcuts or try to grow your own.

Implement User-Level Security.

Take away access from the tables, queries, etc.

Build forms with queries set to run with owner permission.

Build two forms and only give access to the form where changes can be made
to folks who should be able to make changes.



I'd recommend stepping back and doing it correctly. You are always going to
be trying to stay one step ahead of your smartest user if not. You will end
up with someone who knows how to view your code and see your password, or
they will simply go around the form.
 
I have a Main Menu in place so that they have to select the form from there.
To get to the table and guts of the database, a password needed. Otherwise
they will only see the main menu and will not be able to go any further.

I just don't want them to view other records but the manager still needs to.
I am creating a report that the manager can pull from the form which will
open from a cmd button that will activate with a password but I would also
like for them to have the ability to navigate through the records if they
choose not to look a whole report. I would welcome any ideas. I really don't
want to use two forms. I was hoping to set navigate buttons to NO and use the
command button to somehow reset to yes after the password was enter but go
back to no once the form is closed. Am I making any sense? It sounded pretty
good but wasn't sure if it was do-able.
 
table and guts of the database, a password needed - - - How did you do
that? Why can't they simply press F11? Or, hold down the shift key as they
open the database?
 
Again, you probably can do that. I don't know the code right off hand.
Look at the help file and see it there is a property to set those as visible
or not. Also, like I said, just prompt the user to enter a password and
then write an IF statement to see if it is correct. If so, change the
property, if not, issue an error.

This is most likely possible, just very easy for the user to get around.
 
It is all disabled unless they right click on the main menu and select "Allow
Bypass" then they need a the password. One of the programmers who use to work
here developed it and I use on all my databases so only myself and two other
can have the Administrative rights.
 
Ok, I'll try that and give it a shot. Thank you for staying with me on this,
I appreciate your help Rick.

Thank you!
 
Back
Top