We have an inventory application that allows users to add items to the database one at a time.  These are not brand new records but rather records which correspond to pallets where you have to change the quantity in a particular location.  The office would like them to switch to table view and modify several at one time.  So we put a button on the form which switches it to table view but want some way to protect existing data so they don't mess up any other records.  For example some record and error checking when making a change on a field before it is changed completely.  What is a logistical way for handling editing data in such a way? 

 

Thanks

What distinguishes the records they're allowed to change from the records they shouldn't?

You should always try to implement data protection at the data layer.

Fields can be set up with validations that fire before data is actually saved so that when validation fails data remains in the state it was before change.

If the FM validation engine can not work for you then there are things in the interface layer and security/permissions layer that can be used to protect data.