Have you checked the tutorials about importing data
You can import data from another FMP database (which is what this appears to be) So rather than recreating it every week you can just import the data into the table with the yes/no field already defined (and the script saved) and execute.
If you already do the script and field creation yes putting it into a blank file should be easy for you and is the way I would do it.
However you may want to be sure that the import data is all that is in the file you are receiving You may need to do some more work on your "blank" file (This would depend a lot on what your script is doing)
So after following your advice, I was able to import the data and it worked great. Actually better than I thought. However, there is one more than thing that could make this solution absolutely perfect.
I setup the reoccuring import as the video suggested. However, as mentioned above, I have an extra "yes or no" field in my data base that is not in the source file where I get my data from. Whenever I click the script that imports the source file, it erase all of my yes or no answers and I have choose them again. The "yes or no" field is still there, the answers have just been erased." Can I lock this field and have the data from the source field just placed alongside it?
ok in the import dialog box you can set the import action to update matching records in found set in the area between source and target click the arrow on names till it shows and equal sign
the yes no field should see be set to dont import this field
then check the add remaining as new records box
this shouldnt overwrite your data.
If you use the recurring import in a script then you can preform a find at the end to find records that have no yes/no flag
only new records should be this way and your second field could have changed.