icky... It still appears the bug where if window 1. is maximised, and a new window is created (aka a little pop-up window i.e say 200x200) the bug whereby it restores window 1 is not fixed. (i.e adjust window is global to all windows)

Does everyone concur or have I lost the plot? lol

Yes, very irritating. I've been told it's a Windows problem, not FileMaker but I have no idea if that's true. What I've done is size all my windows with a background button or invisible layout objects and ALWAYS use the Adjust Window (to fit) command for sizing. Then multi sized windows work without affecting each other. Just stay away from the Maximize command.

I've also heard it's a Windows problem, but if that's the case, then why can all Web browsers do it?

Especially now that we have menu control, we could provide a pretty slick interface if we could just make filemaker behave like the browsers do.

Rather than minimise windows, why not just close them, and re-create them again when necessary?

I agree...knowing how poor the Windows interface guidelines have been followed I tend to believe this is a typical FileMaker programming problem. Sometimes it just doesn't feel like a Windows program does it? Move a dialog box, the screen doesn't redraw behind it; some dialogs can resize, others can't; sort field def lists but can't sort script lists; lots of silly but irritating things that should have been fixed 3 versions ago. But they don't mind forcing us to pay a hefty upgrade fee for minor changes...very poor business ethics. I just bought Dev 7 and now have to pay for an upgrade to Dev 8 'cause, as usual, they will stop supporting Dev 7 soon. Again, really really poor behavior. They have a very bad opinion of their customers. I know I'm ranting and I could go on for quite some time but when is this going to stop?

Ive noticed also that in the windows version when using "go to related record" script step, you still have to select "open in New Window" or the script wont work. I dont get what the point of this is. If you just define the button as go to related record, you do not have to open a new window.

Officer Ron - Open in new window is an option that you can select. It doesn't have to open in a new window.

This is a Windows MDI (multiple document interface) problem.

Web browsers don't have this problem because they don't use MDI.

Yes I'm aware of that, however if you don't select "open in new window" the script step does not go to the related record. Tis is only a problem in the script step.I'm using a windows platform, I dont know that this is the case on Macs.

Are the parent and child tables in separate files? I have never had this problem when both are in the same file.