Hello MasterMind3,
I did not pay attention to the date of the original post, so my postings did not do any useful purpose in the current sense. Just a couple of further remarks some of which may interest you and please feel free to contradict me.
[1] Do not know why---there must be some web-legend that I see a couple of postings saying window.open is javascript. It is not.
[2] window.open does create an object. So if one is interested in dealing further with that particular object, one does need to set it up properly with
Code:
Set oWin = window.open ([url, [name, [feature]]])
[3] If no immediate interest in calling upon the object so created, you can, as you suggest,
Code:
window.open [url, [name, [feature]]]
with the only detail that you _should_ not enclose the parameters with the parentheses (). Doing so, it would fail.
[4] Just like some top level object app or window, one can spare to call it explicitly, as you suggested. But again, including the parenthese would defeat it.
[5] I only blame the parsing feature that if the name include space (even enclosed in quot""

, the .open fails. That is really bad, and might be considered as a bug. So if the default property name of the window so open containing space, it is much better, as I suggested, to make it in 2 steps:
Code:
Set oWin = window.open (url,vbNull,feature)
or Set oWin = window.open (url,"",feature)
then set its name
Code:
oWin.Name = "xyz abc"
[6] Name does matter if another child window already opened being named the same, no new window will be created. The browser will take that named window to display the thing instructed.
So these are my random remarks which may be interesting to some.
regards - tsuji