How big of an issue would it be to just permanently remove the unique values validation?
Perhaps by substituting a different validation method via a script trigger to do the same thing?
Yeah, that's an option, but I'm hoping to avoid that if possible. It's just a little cleaner without the extra script trigger and remembering to put it on all the layouts where the field can be modified.
I wouldn't want to either, but suspect you won't be able to avoid it...
Hmmm, this is really taking a weird approach, but what if you defined a second field as an auto-calculation field that duplicated the first field's value and you set a unique values validation on it? that puts it at one remove so you can remove the validation rule from the original field and your SQL can then re-index the field, but FileMaker still enforces the validation rule on your data...
As a little background, one of the reasons for re-indexing certain fields is that we're experiencing some stability issues. We're doing a bunch of things to help with that, including removing calculation fields where possible. So, adding another one to the mix may not be the best idea.
But I'll keep that trick in mind for the future. Thanks for all the ideas!
FileMaker 11 can use advanced recovery options to re-index all the fields in your database in one batch go without making any other changes to the file:
- With the file closed, select Recover from the File Menu.
- Select "Use advanced Options"
- Select only: "Copy File Blocks as-is" and "Rebuild Field Indexes Now".
Yeah, I think we may end up going that route. Part of the issue was that only reindexing some of the fields was faster, but it was also quite a more work. With the extra work involved in the partial reindexing, I don't think it's enough faster to justify the effort.
Thanks for all of your help!