It sounds like you would benefit from having an "EquipmentStatus" field that can be set to Active or Inactive.
Your "Graveyard" would be all equipment that is Inactive.
Your current relationship would then be
UEquip::Code = EquipMovement::Code
UEquip::gStatus = EuipMovement::Status
where UEquip::gStatus is a global field set to "Active" in your startup script.
For additional reading on this, check out the topic "Portal Filter"
Just for terminology sake,.,..you aren't removing anything from a layout...or even from a Table...you are filtering the portal to filter out "Inactive" Equipment.
Thanks for that - I will give it a try. I do, however, want to move the Graveyard equipment into either another layout or into another table as we will need to be able to export all the details on these pieces of equipment and be able to easily look them up.
Although I am filtering the portal in the UEquip table (thanks for the terminology there :-)), I am wanting to actually move it out of the standard layout in the Equipment Movement layout so that when we go through the records to look at what works have been done, we don't have to go through these. I realise that we can do a search but I am trying to overcome a need for a user to do this so only want to show active equipment. Although this may seem like an odd requirement, it is what the boss has asked for...Is this possible somehow?
You do not and cannot move any data out of any layout. You can, however, move the data out of the layout's underlying table. But this is not necessary to do what you want here and doing so adds unnecessary complications to your design.
Exporting details and easily looking up data on the active or "graveyard" equipment is quite easy to do and does not require exporting those records to a different table.
PS. In FileMaker, when you create a new table, the system automatically creates a table occurrence--a "box" in Manage | Database | Relationships and a layout with exactly the same name, but these are three different objects with three different "jobs" in your database. A table is where the data is stored. A layout is a means for accessing the data stored in the tables and a Tutorial: What are Table Occurrences? is a means for establishing a relationship between a given table and other tables.