Why do you need that additional table? In fileMaker, you, as the developer can manually create additional tables. You can use FileMaker Advanced to copy and paste a table definition. In both Regular and Advanced versions, you can use Import Records with the New Table option to create a copy of an existing table and it's current found set of data.
But FileMaker is not set up to dynamically create/delete tables in response to the general user interacting with the database and that isn't something often needed anyway.
Usually, "subsets of a table" are treated as different groups of records all in the same table. Unlike the "recordset" of many other DB systems, FileMaker's "foundSets" are a lot more dynamic-with many user initiated ways (as well as those we as developer set up) to pull up different subsets of records to for review and editing or for a report.
Thanks for responding! I really appreciate it!
I think I understand what you are saying- just to be sure, it sounds like I can set a flag in a table to distinguish different types of tables? This way I can use portals to see the different types by changing a parameter and matching it to the flag?
You can set values in fields to identify records as being members of different categories. And then there are a number of ways, a portal being just one option, that just the records from one category will appear in the portal.
One trick that I've used is to set up the category field used as a Match field in the relationship and place it as a check box formatted field near the portal. Selecting different check boxes then changes which categories are visible and if you select several check boxes, you get all of the selected categories.
But many other options are possible--including layouts that automatically limit you to records of a given category and settings in Manage | Security that hide records from the user (with a bit of added scripting) if they are not authorized to view them...
Thank you so much! I really appreciate it!