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.
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. 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:
Finally, the most elegant solution: create a new ‘active records’ table and put it in front of the real data table. Store only primary keys in that active records table and link it to the real data table via a one-to-one relationship. Here’s an example with an article table where you want to hide obsolete articles:
Create the Article table the same way as usually, but DON’T activate the serial number auto-enter option for the __id field. Then, create another table, ‘ArticleActive’ and define only one field: the __id field there, with the serial number generation turned ON. This table will contain one record for each active article. Here is what the Relationships Graph should look like:
Here’s how that relationship is set up:
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. Instead, the related data is untouched. It simply does not show up in the main table due to the lack of a matching record!
This is a great example of thinking outside the box by Jan Zelenka of ClickWorks. Read the whole thing and download the sample file.