![move field to another table filemaker pro 10 move field to another table filemaker pro 10](https://manualmachine.com/html/69/69ce/69ce6c4bae7a1c542ed5fc8a33491fdeeb6860e5ca36106aa70ef6497f913591/htmlconvd-p5saSw15x1.jpg)
It simply does not show up in the main table due to the lack of a matching record!Ī challenge for those out there using Todd Geist’s Selector or Session model: How would you integrate this restore technique into those models? Since the context is always on the table with only the Primary key, if that record is deleted, it appears that all of the data is deleted. Here is what the Relationships Graph should look like: This table will contain one record for each active article.
#Move field to another table filemaker pro 10 serial number
Then, create another table, ‘ArticleActive’ and define only one field: the _id field there, with the serial number generation turned ON. Here’s an example with an article table where you want to hide obsolete articles:Ĭreate the Article table the same way as usually, but DON’T activate the serial number auto-enter option for the _id field. Store only primary keys in that active records table and link it to the real data table via a one-to-one relationship. The new table has only the one primary key – all other data is pulled into the layout from the table with containing the data through the relationship:įinally, the most elegant solution: create a new ‘active records’ table and put it in front of the real data table.
![move field to another table filemaker pro 10 move field to another table filemaker pro 10](https://img.yumpu.com/20834848/1/500x640/contents-filemaker.jpg)
The secret is to put new related table in front of the table with the data, and relate the new table to the old table based on the primary key. Instantly Restore Deleted FileMaker Records? How is that possible? As it turns out, it’s not that all that hard, but does require some up front planning.