Ghost records appearing in portal

I am having a major issue with records showing up in portals where they shouldn't be.

I have a relationships between two tables where this is occuring. Although there are 4 tables involved.

There is a BOM Baan Connection table and a corresponding BOM Table, then there is an Item Master table, and an Item Master Baan Connection table.

The exact same data exists in the Baan Connection and non baan connection tables. So the Item Master table and Item Master Baan connection table have the same data, I did this to allow for a revision control system (although now that I look back on it I hsould have used one table and just used a single field for control), anyway, after I run the script that imports the data and then copies any changes over to the other table, I want to display the information in a portal.

The BOM Table has three fields of importance. The Item Number field and the Component Item Number field. An Item Number has both formula and Packaging information. The kicker is, all three of these "types" item, packaging, and formula have the exact same fields and are all listed in the Item Master table. Second of all. There are multiples of the Item Number for each component number. So say you have an item number with two formula items and two packaging. That means you would have that item number listed 4 times in the BOM table, one for each component item. Also, there is only one way to differentiate between the different types, that is based on the first two digits of the id numbers. So a packaging number will have the first two digits differ from a formula type. You also can have formula types that are also item types.

So I created a calculated field in the item master table that checks the id number and then sets it to one of the three types, packaging, formula, or item. I then set three static fields in the BOM Table for each of these three types. I then set up a relationship between the BOM and Item Master table between the BOM::Item Type and Item Master::Type fields as well as the BOM::Component Item Number and Item Master::Item Number fields. This allows me to display the formula and packaging, or item information in portals on the screen. The issue is. You know how in my example I had 4 component items? Well, the portal is showing more than just 4 component items. It is displaying item numbers that don't exist for that main item number. I am really at an impass here because I have no clue how to solve this issue. A woman I talked to two has used filemaker for years said that it is probably a relationship issue, but I cannot see anything wrong with the relationships I have set up. Has anyone else had any issues like this before, with records showing up where they shouldn't be?

Thanks.