November 9, 200619 yr Say you have a layout in a parent file that shows a portal to the child file. When you open the parent file, the child file will open "hidden" -- it shows in the window menu as (child) with parentheses. When you select the child so it's visible and then close it, it doesn't actually close, because the portal on the parent layout forces it to stay open. So it goes back to its hidden state. That makes sense. But suppose you go to a different layout that has NO fields from the child on it. You would think that at that point you could bring the child to the front and close it. Nope! The only way to close it is to close the parent file. Even when you have NO relationship between the parent and child tables on the graph, the same thing happens. I.e. you don't have a portal on a parent layout, but you do have a child table occurrence somewhere on the graph. (Which you might want so that you could go to a layout based on the child TO, then go back to a parent layout, and then close the child file. In fact this is what I want to do.) The only scenario that allows closing of the child is when you have only a file reference to the child (so you can open and close it with scripts) but NO table occurrence of the child on the relationship graph. Does anyone else think this kind of sucks? Sample file attached, but feel free to create your own test files so you can see there's nothing else going on, nothing up my sleeves, no open/close scripts etc. stickyfile.zip
Create an account or sign in to comment