>>>>
>>>>I like the default as-is. I just don't want a message requested in one window appearing in another ALREADY OPENED window.
>>>>
>>>>I don't see any need to have new/changed defaults from what already exists. And if it really requires that kind of a change, then forget about it.
>>>
>>>The link "target" was the "message" frame when using the "map" button.
>>
>>Seems that something is amiss (buggy) when something initiated in one instance of IE can end up in some other already extant instance of IE. I thought that the object model guarded against this kind of thing.
>>
>>And it looks like the Map has a 'target' similarly, yet it comes up in the expected (newer) window.
>
>Its not a UT bug, its a IE feature :-)
>
>When you work with frames, you have to give a name to each of them.
>This way you can have a link in one frame that "target" another frame.
>
>Internally, a frame was a kind of window instance for IE,
>so the link can find the target frame between distinct IE windows.
>
>BTW, another tip: you can shift+click on a link to open it in a new window,
>its more direct than the right-click method :-)

Not to drag it out, but one more question...

If the link target is the message frame when using the map button, and the link target for a map message is the message frame, why does one stay in its window and the other migrate to another?