You'd need to tell us more about context.
If this worked before, might this be a solution that consists of more than one file? If so, you might have a file that is missing or not in the same place that it was relative to the other files as it was before you had to restore everything.
But looking at you relationship graph, it looks like __kp_JobID needs to be an indexed field judging by the naming convention used and the "connector type" shown in the relationship graph. (A "T" connection shows that the field is not indexed--either defined as not indexed or defined as a global field.) You may need to go in and turn on indexing for that one field.
Thank you Philmodjunk!
Apparently when I was trying to re-build the indexes, I had a difficult time getting the changes to commit while managing the database. After tinkering with it a bit more, the changes do not commit when I check the validation for unique values. That is another glitch, but at least I am back up and running for the time being.
After tinkering with it a bit more, the changes do not commit when I check the validation for unique values.
Could it be that you are expecting something that FileMaker doesn't do? Changing a validation option will have no effect on records already present on the table unless/until that record is again edited. The changes will thus only seem to "take" on newly created records.
But you also cannot validate for unique values on fields that are not indexed--that includes fields with global storage specified.
And fields of type calculation ignore all validation options as these are not applied to calculation fields.