Deletion prevention

[Valerie J. Breitbach]

I recently had to fix up some 'orphans' because a record was deleted. (I am still trying to work out just how & why she did what she did!)

I would like to prevent the average user from deleting anything. I want 'deletability' to reside only with me, (or my one on-site trustworthy computer-worthy individual).

Thoughts?

Thanks!

P.S. Prior to a pack is there a quick and dirty way to see deleted records?

[drgarytraub]

RE: Deletion prevention

Valerie:

There are many ways to do what you are asking, but one simple way would be to put something like this in the button that will delete a record:

dim pw as c
pw=ui_get_password("Enter password","")
if pw="valerie" ' put any password you want
put code here to delete the record
else if pw"valerie"
ui_msg_box("You are not allowed to delete records","")
end if

Gary Traub

[CALocklin]

RE: Deletion prevention

Here's a couple idea starters:

(1) You could create a log-in requirement with passwords and only allow changes, deletions, or any other desired actions based on the security level that you assign to each user. The downside is that it takes a fair amount of effort to build such a system and set up each table/form/button to recognize the security levels and act accordingly. The is probably the most foolproof method but it isn't a 1/2 hour job. (I have two apps that use something like this.)

(2) A 'down and dirty' method might be to create two sets of forms (create 1 - copy and paste the 2nd!) and the normal user's forms could be set to restrict deletions. The forms you use would have to be password protected in order to load them. This password protection would have to be in the OnInit script. (Suggestion: create one global script and use 'script_play("...")' in the OnInit to run it.) The downside to this is (a) users will probably be able to find a way around it if they really want to by going to browses or opening default forms, and (b) your second set of forms will need to have different names which could interfere with scripts. How much time this takes to set up depends on how secure you want it and how 'integrated' your forms are.

This just touches on the subject. Hopefully others will add their own ideas, experiences.

[CALocklin]

RE: Deletion prevention

OK, now that I've spent all that time writing, I realize I missed the obvious!!

Put a script in the CanDelete event of any table you want to protect. Here's a really simple one you could use:


pw = ui_get_password( "ENTER PASSWORD", "Please enter the deletion password.", "****", "****" )
IF pw ""
cancel()
END IF


One warning: I've never tried this in a set with referential integrity turned on. You may end up with multiple password requests - one for every child table deleted.

And a recommendation: Again, make this a global script and use 'script_play' to activate it. The reason is that you can then change the password only once it someone finds out what it is. You might also want to password protect the global script.

[CALocklin]

RE: Deletion prevention

Oops. That script didn't come out right because I didn't create the " signs correctly. Here it is again:

pw = ui_get_password( "ENTER PASSWORD", \
"Please enter the deletion password.", "****", "****" )
IF pw "> ""your_own_password>"
cancel()
END IF


(In case you aren't aware, the "\" is the continuation character to mark the end of a line that is to be continued on the next line.)

[JohnZaleski]

RE: Deletion prevention

Try declaring a global variable ( eg. OKAYDELETE ) in your app entry form.In the "candeleterecord" event in field rules for the appropriate tables, only allow deletions if the VAR->OKAYDELETE = "OKAY". Have a hidden button on some form that allows you or your key employee to put the "OKAY" value into the variable. You will have an identical field rule that can be copied and pasted and repasted into the field rules of all tables. I do this for some deletions and changes on critical fields.