It has been a little quiet in ‘the soup’ over the last couple of days, so a job we’re towards the end of has lead to this question for a bit of discussion.
The project is an integration from a multi-file design from the 1990s into our SaleFaith structure. All validation in our current systems is scripted, as are the majority of calculations, summary fields, etc, but the old files rely on unstored calculations, field level validation and many other techniques that have been replaced by features from newer versions of FileMaker (I’m not suggesting calculations and field level validation shouldn’t be used, they just aren’t by us).
To my point. I was caught out by entering Find Mode, because a field from an old table we’ve imported for data migration failed validation, which lead me to wonder whether people are error trapping for every eventuality that something like a validation failure can cause.
For anyone not on my wavelength; when using field level validation with Error Capture set to ‘On’ every instance of ‘Go To Layout’, ‘Enter Find Mode’, ‘Go To Related Records’, ‘Go To Record’ and no doubt many more I’ve not listed can prevent actually leaving the current record.
The worst example: an instruction to leave the current record using one of the above methods, validation prevents this, and the next scripted instruction is ‘Delete All Records’.
Finally to my question. Does everyone error trap for every instance in every script for all of the aforementioned leave record script steps? My belief is, that if you use field level validation, then absolutely you should, otherwise pain is inevitable in the future.
I do acknowledge that field level validation and protection is the most secure method of protecting data and enforcing rules, but don’t want to get into that here now, as it will distract from the above question.