Data Safety

[ConanTheLibrarian]

Ok, thanks to other posters on the forum, two of my three database issues are now resolved, one without needing its own post. Now, for one final consideration:

This db will be used by people who are not Access-savvy. That was always the idea. My question is: how can I set it so the form allows them to EDIT records in the db table, but not to DELETE them?

I'm projecting that a knowledgeable someone could, if necessary, go into the table to delete a record as needed. The average user will just be editing existing entries, not making sweeping changes to the overall data structure.

Is the lack of a "Delete Entry" button on the form sufficient to this task or will more be needed?

Thanks as always for the input!

 

[pbaldy]

The form has an Allow Deletions property that you can set to No.

 

[Galaxiom]

One handy enhancement is to pretend they can delete. Add a Boolean field to indicate the record has been "deleted". Records flagged as deleted are excluded from the RecordSource query of the form.

When they press the delete command button the record is simply marked as deleted and the form requeried. It is a very simple matter to bring the record back again.

 

[missinglinq]

In point of fact, many of us use Galaxiom's method and never actually Delete Records.

Linq ;0)>

 

[ConanTheLibrarian]

Thanks to all for the help. That "Allow Deletions" property was what I ended up going with. Maintaining a record history may be useful in other applications, but would be redundant for this one (though I AM squirelling that idea away for a rainy day).

Again, thanks a ton for the help. =)

 

[pbaldy]

Happy to help!