DD Validation Bug IMHO
We've spent an unproductive few hours trying to work out why a dbComboValidation table didn't work, and finally found a reason.
If the PREVIOUS value of a field isn't in the codemast it throws an error (presumably on the backout) but of course the user only sees the error as being with the new value. Our old bluescreens didn't validate as much as we do now, so every once in a while an invalid value is found. Fixing it throws an error.
Why validate old values when they are being replaced?
19.1
Last edited by DaveR; 14-Feb-2020 at 11:29 AM.
I should be on a beach ...