Custom Message Box

[tallboy755]

Is there a way to have a message box pop up at the begining of a script asking ... "Are you sure you want to delete all records" .... and (here is the catcher) If they click yes ... the script continues or if they click no the script exits?

[ernst]

Start script with

Show Message ["Are you sure you want to delete all records?"]

If status(CurrentMessageChoice) = 1

Exit script

End If

Delete All Records

:

:

Ernst.

p.s. Make backups!

[tallboy755]

again ... A+ .. love ya all

[Ugo DI LUCA]

But these steps ae already existant in FM.

Delete All records (no dialog) script step.

So

Show Message "Do you want to delete"-Yes/No

If Status(CurrentMessageChoice) = 1

Delete All records (no dialog)

Else

Exit script.

God I'd never use such a script in my solutions !!!

[AudioFreak]

Ugo,

Re: God I'd never use such a script in my solutions

May I ask Why?

Michael

[Anatoli]

I never let users delete even single record = no problems with my solutions

[Ugo DI LUCA]

Suppose your user get distracted and push the wrong button....

The delete all records with no dialog is one of these script step I try to avoid. At least keep the dialog...

My opinion of course. Certain automation still keep me afraid.

[Lee Smith]

Why Ugo,

You don't trust your users.

[Ugo DI LUCA]

Agreed...It surely depends about the business though. You surely need some delete steps, but I'd prefer to have more caution on how it is done, with 3 dialog alerts, a bip and a big surprise at end-month for that user that by-pass such rules...

[AudioFreak]

Agreed!!! These are the types of answers I was looking for. Where I work the users complain "why do I have to come to you just so I can delete a record", "I'm not a little baby". Then I explain that it is for the safety of the database and all the company information enclosed. I just have them flag a field which I check at the end of the day when doing backups of our files. Thanks for the confirmation on this. Just a little more fire power for the boss.

Michael

[ernst]

Come on guys, not everybody makes databases with only 'highly sensitive business information' in it.

[AudioFreak]

Hghly sensitive or not. I don't want to have to deal with importing the last backup and not to mention the records that will be lost that were created since the last backup. In some instances this can be 100's of records.

[Ugo DI LUCA]

Don't you ?

Every single record, when deleted, is lost... , and involving the backup upsets me, and sometimes isn't sufficient.

Really, even with my personal CD db, I have 2 cautions, and I'm thinking of a new third one which could be "Planned a trip to meet Anatoli in Prague in March ??"

[Ugo DI LUCA]

Audio, we surely should work together

[AudioFreak]

Maybe I should go to Prague and meet Anatoli also

[ernst]

Database Programmers Unite Against Deletion!

[tallboy755]

Ok ... ok i am compelled to respond with my explanation ... I have a database setup for just simple viewing ... no editing ... nothing like that ... i have about 100 data files that someone can import (open) into my database ... however when they open the next data file they must first delete all records in the file ... Just simple viewing ... thats all

[Lee Smith]

Your use of words here of import and delete are confusing to me.

It sounds like you have two files, one for viewing the information of data in a second file? Wouldn't this be easier accomplished by using a relationship?

Lee

[stanley]

One thing I do in this kind of situation is to put the users through two dialogs, the first of which they have to click the default button on the right, the second of which they have to click the non-default button on the left. This way, distracted users & lazy people who just slap the enter key every time they see a dialog box don't do any harm...

Another thing you can do is to export the records that are going to be deleted - there have been a few times where users have deleted records & when they claim they did not, I've been able to show them that the export file on their (client) machine contains exactly the records they claim not to have deleted - therefore proving that they did indeed delete the records. It is simple to recover the data, although any image/sound files embedded in the db are lost, but they should be (and in our case, are) backed up elsewhere anyway.

-Stanley