That is certainly one way to do it. Why do you need to? (Usually, it's easier to add new records in the related table on an "as needed" basis while editing your data instead of using such a "batch" update operation.)
We have accounting company and have several tasks that should be done monthly to every customer. If we add these jobs to table at the beginning of every month or year with status "open", then we know customers whos job is not done.
I have done inhouse programming as part of my job about 15 years with Delphi. Now we are considering to moving Mac world and needed solution to made inhouse apps to Mac. FM seems to be right way. I started learning FM by making small payroll app. First i thought that i need time to complete it about 2 weeks. I managed to get it working next day, still learning how to use FM :) And it also works as IWP in web!
You may also be able to set this up with an Import records operation that imports the ID field from the customer table into mathcing field of the related table. This will create a new, possibly blank record in the related table for each customer record present in that table's found set at the time you perform the import.
Import Records operations should be done cautiously with backups made just before you do the import. If you cannot match the fields by name, and this is a scripted import, future design changes to a table can create a really bad situation, so be careful if you choose this option.
For More Information on this import bug, see: Data loss bug : Spontaneous and erroneous import matching of new fields in specified imports !
This is one of many acknowledged bugs that can be found in the Known Bug List here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: http://www.4shared.com/file/8orL8apk/FMP_Bugs.html