Hi Bruce,
Thanks for your help. By "FrameSet" procedure you must be refering to FramePage? (I copied from the examples.) If I put 'FramePage' in for the URL and '_Top' in for the TargetFrame (for the Save button) it then opens up a whole new browser page and now there are two separate browser pages open with my app's framepage in them. If I take out '_Top' and leave it blank, then when Save is clicked a new FramePage opens up inside the original FramePage with a whole new MenuOnLeft, etc. In fact, if I leave the URL line for the Save button blank or enter anything other than 'IndexPage' in the URL line, clicking the Save button causes a new FramePage to be opened up within the original one. Only 'IndexPage' in the URL seems to work at all properly for me. I think there must be something set wrong somewhere in my app although I have checked all the settings in IndexPage, FramePage, MenuOnLeft, and ChangePWForm a thousand times and I can't see anything different from the examples.
If I don't have the URL set to 'IndexPage' for the Close buttons in all the other procedures that are called from the MenuOnLeft procedure I get the same weird result where the menu or the framepage is opened a second time within the original FramePage. In fact if I continue running procedures it nests more FramePages! Can you give me a hint of what might be causing this behavior?
I use IE7 and am testing on the LocalHost.
Thanks for any help you can give me. By the way, I am looking forward to your Webinar tomorrow!
Cheers,
Jill