You will need to examine what you are trying to do with your database more before we can get pointed in the right direction. It also would be helpful for you to review the FileMaker Training Series Basics http://info2.filemaker.com/FileMaker_FTS14_Basics.html. Your explanation sets off several warning flags with your use of the name as the key and your use of repeating fields. It looks like the functionality that you are trying to use the repeating fields for could more easily be done with your related table.
THat should read that you will need to explain what you are trying to do.
it is only an example, I can easily have 3 fields for LOCATIONS and 3 fields for GUESTS instead of 2 repeating fields, or whatever.
The issue is: how to automatically generate and update fields in the related TableB based on values on TableA and that is not part of the Filemaker Training Series Basics.
The easiest way is to use a portal into table B and not have the location field in table A at all unless you were using a self-joining table occurrence.
"it is only an example, I can easily have 3 fields for LOCATIONS and 3 fields for GUESTS instead of 2 repeating fields, or whatever."
Yes. It is an example.
It is an example of trying to solve a problem which should not exist in the first place, and which results directly from poor data structure.
As mentioned by Blue22; use the Training Series to learn how to build a more effective design.
Blue22 and Bruce,
after using Filemaker since version 4.0, if I would/could use a portal I know exactly how to do.
The reason of my question is exactly as addressed: how to create/update records in an external Table since that file cannot stay in the same server/location as the primary file. TableB should be used as a stand-alone file periodically updated and then used elsewhere.
No your question still isn't very clear.
How are you hosting the files that these two tables are in, two separate FileMaker servers, two FileMaker Pro clients? You seem to be connecting the files to run the script why can't the external tables be connected? Your question seems to be moving toward a syncing question instead of a creating/updating records in a related table question.
Both TableA and TableB are in the same computer.
TableA is primary file with all fields and all records.
TableB has only specific fields and specific records. It needs to have all records separated as previously explained.
TableB needs to be copied in portable computers and used elsewhere offline as stand-alone.
Once a week TableB needs to be updated with changes performed in TableA and copied again and so on.
The question remain the same:
"Do you think the only way is to redo a loop script every time values are changed in TableA (which is what is done until now but not very handy with over 100.000 records) or is there an easier/faster way to make TableB automatically updated?"
If you have been managing so far with a looping script, then keep doing that. To deal with the "thousands of records" issue, surely you could devise a way to find only the records that have changed since the last update, and then loop through those.
You probably should research SYNC-type solutions.
#4 (third party tools that I found):
(a helpful blog that I found):
Great resources as always!
""Do you think the only way is to redo a loop script every time values are changed..."
But your question is still not clear.
Is the question about re-RUNNING the script when values change?
Or is the question about re-WRITING the script if structure changes (more repeats added for instance)?
no there no need to re-write the script since the owner of the database is happy with actual.
I was just wondering if there is a "more elegant" way to have things updated automatically.