Many to Many Troubles

[sflynn]

I am stuck trying to relate a many to many relationship.... Can you help me?

I have a project table which is the parent. Then I have a Location table but a single location can be associated with multiple projects. So I used a join table to create a record that links up the location with the project... works great. I also have an "asset" table that works the same way with the Project table (an asset can be associated with multiple projects). Then, I have the assets linked to the Locations with a join table too because each asset can have multiple locations.... That all works fine(I think). I have portals going between them all and it seems fine. Until I go back to the project and try to get a portal to show all locations related to the parent. The way I have it now is that there are two join tables for locations and I want to be able to have all the locations for a project come up in a list regardless of whether they were created between the assets and locations or the project and locations? This is just the first level because I want to link others up ... what am I missing? Any help much appreciated!

steve.

[Ender]

It's not clear to me why a Project-Location would not cover the requirement to know the Location of the assigned Assets. The bottom line is a given portal can only show the records from one table, so you may have to give up on the combined portal method, rethink your requirements, or come up with some scripted technique to build a combined Project-Location table just for this portal (not something I'd recommend).