Filter vs. SQL Record Source

[Randomblink]

I have built my tables with two extra fields.
del_Rqstr - Username of person requesting deletion of record
de_Rqstd - CheckBox (Record Requested To Be Deleted)

The reason is, my client doesn't want her users to ACTUALLY delete stuff. She wants to be able to see who deleted what and when. What I currently do is, whenever a user hits the delete button, it checks the checkbox and grabs their NT username and assigns it to that deletion. Then, each form has a recordsource in SQL that ONLY allows the users to see accounts where del_Rqstd IS NOT CHECKED... This way, when a user 'deletes' a record in any given table? It doesn't ACTUALLY delete it... It logs their user name and makes it invisible to all other users.

I am wondering if anyone has ever run across anything like this? Have a better idea? I know that I COULD have used Filter, but I am afraid that if a user did the right filter it would show them that they are NOT actually deleting records and they could do something about it.

Currently, the database I am working on is SPLIT. The backend is on the server in a hidden folder, so they can access it, but they can't see it... The Front-End which houses the forms and reports and linked-tables, has code that locks the user out of being able to get behind the forms. They are unable to see tables, or modules, or anything else... They are also locked out of the design view of everything.

So, with ALL that in mind... anyone got any ideas? Or have I got it covered?

 

[SQL_Hell]

Sounds like quite a good solution to me, but really you could have just set the permissions for the users to not allow deletions on the specific tables.

What happens if they do actually want to delete data.

 

[Randomblink]

What happens if they do actually want to delete data.

The BOSS has a special front end with full access to tables, can click a button to show JUST the records that have been 'deleted' and SHE can do the actual deletion...