File > Manage > Databases > Fields.
Pick the field you want to validate.
If you go into the "Options" for the Field (bottom right) there is an "Auto-Enter" tab in at the top of the window.
Click "Data" and type No into the corresponding box. Works a charm for me doing the exact same thing as you want. :)
Thanks a million for your reply--worked like a charm for me as well!
Happy to help. :)
Sorry to have to bother you again but after formatting the yes/no box for a default 'no', the first few records showed the 'no' but others did not.
When I went to Manage, I highlighted the field, it said 'text' and 'options', I clicked on 'options', checked 'data', put 'no' in the box next to 'data' and got the occasional default showing, though it should have shown on a lot more than a few records.
Auto-Enter only works on new records created, it does not change current records.
Thanks, S. Chamblee--that makes sense. I'd entered data before adding the field and I can see why manual input would be important. Sorry to have had to bother you with this.
I have been stupidly busy past few days - hence the no help.
I ran into the same problem and I had around 300 records that I needed to set to "Yes" or "No".
What I did was:
Check how many records you have that you want to set to the default value (I would presume all of them for now).
In Excel I made a field with the same name as the field in FileMaker that we are working on.
In Excel: I copied the default value (No) and selected all the 'records' under the field name and pasted the default value into them.
At this point I had a correct version of the yes no field but in excel.
Filemaker > File > Import Records > File... > select your excel spread sheet.
Work through it and when you get to the settings you want to
"Update Existing Records in Found Set"
"Don't import first record"
and change the Arrange By: Matching Names
I hope this helps. :)
You can use Replace Field Contents to update a field in a group of records within FIleMaker. Much simpler than the import method described here!
Thanks for your reply (I was traveling, else would have responded earlier) and I'll try your method. It also occurred to me that maybe I could create a clone of the existing database, change the field properties, and then import the data, which I might try as well.
Thanks for your suggestion, seems a lot simpler than what I was contemplating, and I'll give it a try.