Well, I'm trying to look at stuff managed by uniface in the dict model, so I'd have to run a thing that built the intermediate entity somehow. I was looking to write a report to basically show "this is where the same menu in a non base language differs from the base menu" 
 
I am aware that the canonical many to many relationship has an intermediate, but I'm looking at this relationship for reporting rather than database management purposes. Normally, where a relationship did not exist, I could put a job-specific u_where clause in the entity to get the report component to read the correct one, but I can't do it here, because it appears that the inherited relationship from the parent entity is in place, and enforces the language being the same, when I want it to be different. 

I have a menu called "SYSTEM", in a library called "GLOBAL" in three languages, "USA","AME","SIN". 
I want to paint (from the dict model) USITEM and USMENU twice, and have the system retrieve the outer one based on the language being USA, and then a related one based on umenu, uvar & useq being the same, but ulan being different. so I can then compare and contrast the title, predisplay and option triggers. 
I can't do this in sql or crystal because the fields I want to play with are held in the ucomment database field, (and overflow table). 
I can't do it in uniface (without creating this table I'd have to maintain myself) because I can't detach the relationships. 

Could I paint a dummy table inside the outer usmenu, and then put the inner usmenu inside it, would that break the relationship and (basically give me path to XXXX not found?)

Iain