[AccessD] Transactions

Thanks, Drew.  Well, I guess it depends on what sort of users you are 
dealing with.  At the risk of re-hashing a discussion that has probably 
been done before, I think there is a distinction between functionality 
in the application when it is being used in the intended way, and 
deliberate unauthiorised attempts to circumvent the intended 
functionality.  In terms of the original question asked by Arthur, where 
he wants the users to be able to add new records but not delete or edit 
existing records, I can open a form in design view, set the Allow 
Deletions and Allow Edits properties to No, and close and save the form, 
in less than 10 seconds.  My time is valuable, so this is an important 
factor.  If that form is the only way (apart from unauthorised hacking) 
for the data to be accessed, then that would be perfectly adequate in 
the case of all the clients who I have ever worked for.

Regards
Steve


Drew Wutka wrote:
> Show me a way to truly prevent it.  It's there whether you like it or
> not.  Disable the Access Keys such as F11, and you just have to go
> through the Window Menu.  Even hiding the Access Window itself doesn't
> guarantee a curious user can't get to the database window.  Heck, the
> code to unhide every Access window on your machine is just a few lines.
> 
> User level security isn't hack proof (nothing is), but it is a lot
> stronger then 'hiding' the database window.
>