Halt before going to another record

[khfudge]

I have a client working in 8.5 who has requested specifically a "halt before going to another record" (his words) message that would remind the user to check certain fields before leaving the record. I know that I can set these fields to validate ... not empty, etc., but he just wants a message to remind the user to "eye-check" these fields to make sure that the correct data is entered and choose to continue or return to the fields before going to the next record.

 

Any suggestions? Is there a way to run a script to send a message before exiting the record?

 

Kathy

[Techphan]

Is this what you mean?

 

1) Hide access to the different layouts from the user.

2) On the first message layout ("Warning..") change all of the fields so that they cannot be entered.

3) You could put a "Close this message" button in the red box (and make the other button underneath inactive) instead of using the button under all of the fields, but it still takes you to the next layout.

4) You can add a "Cancel" button that returns you to another (previous) point in your process.

 

Written in FMP8.

[khfudge]

No, when the user commits the record and attempts to move on to another, the client just wants a custom dialog to pop up with a message similar to, "WARNING: Please double check greeting field, follow-up date field and user initial field to make sure that they are correct." and then a return to record or continue to next record button in the dialog box. But, this doesn't necessarily mean that the user entering the data just won't make the decision to disregard the warning.

 

It's really not worth a lot of time or an extravagant script, I'm thinking the best recommendation and easiest way is to set these fields individually with validations of "not empty" or "member of a value list." I believe that this is the best protection in order to ensure that fields are completed. I don't believe we can ever ensure that data entered is absolutely, positively correct ... we can only do our best to get the user to enter properly and give the client a database with integrity.

[Norma_Snockurs]

You could do it like this:

 

Pick any field on your layout but perhaps one that is pretty much always edited at some point. It's not really critical as long as it is user editable and exists on the layout.

 

In Define Database set the validation for the field to 'Only during data entry' and check 'Allow user to override during data entry'

Require: 'Validated by calculation' and specify the calc as

 

not Get ( RecordOpenState )

 

unchecking 'Validate only if field has been modified' at the bottom of the window.

Finally check 'Display custom message if validation fails' and enter your message so:

"WARNING: Please double check greeting field, follow-up date field and user initial field to make sure that they are correct. Continue to next record?"

 

Now, whenever any changes are made to a record - or it is new - and it is saved either by clicking on a non data-entry area or moving to another record, the user will be prompted with your warning and given three options: 'Revert Record', 'No' or 'Yes', so the wording of your message needs to work in context with this behaviour.

 

However, method aside, I think your users will get annoyed with this behaviour pretty quickly and will end up just clicking the 'Go Away' button by default. It is a frustrating fact of software development that users DO NOT read dialogues. I know developers imagine themselves having this ongoing dialogue with the user as they navigate around the solution but in reality hardly anyone reads dialogues. I watch people using solutions I have developed all the time and, frustrating as it is, they just don't do it.

 

This is the point where usually someone like Ender will chip in with anecdotes espousing the merits of minimal or no validation and avoiding dialogue text of over three words long. I have to admit that it's probably the best course of action. Every time you think that a dialogue should come up ask yourself if it is absolutely and unavoidably necessary. If it is can it be done in two words? Your users won't thank you for an essay everytime the solution needs to branch one way or another.

I don't believe we can ever ensure that data entered is absolutely, positively correct

Well you can with numbers and dates but most text is pretty impossible to police 100% effectively. There's a lot to be said for training users in correct procedure and making sure they understand exactly what is expected to be entered in fields.

[khfudge]

Thanks Norma ... I think this might be just what he's looking for. Unfortunately, as a developer, I agree with your statement, "I think your users will get annoyed with this behaviour pretty quickly and will end up just clicking the 'Go Away' button by default."

I'm going to bring this issue to the client's attention before proceeding.

 

Again, thanks a bunch to all who have helped with this!!

 

Kathy