Jump to content

Security for edit register (part II)


This topic is 8571 days old. Please don't post here. Open a new topic instead.

Recommended Posts

ExactUpdate:

Don't allow the record to be edited unless data in the field with the ExactUpdate restriction submitted by the Web user exactly matches the value that is stored in that field.

This is the way I use it in one instance:

<INPUT TYPE="password" NAME="Password" VALUE="" size="8">

where Password is the name of a field in the database and each record can have a unique value. When the user wants to update a record, they make the changes in the form, type in the password, click the submit button and if the data in the password field matches the data in the password record's password field (and that user has edit permission for the database), then the update is accepted.

[This message has been edited by dspires (edited December 01, 2000).]

[This message has been edited by dspires (edited December 01, 2000).]

Link to comment
Share on other sites

This topic is 8571 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.