🚀 go-pugleaf

Try the Interactive user launch setting.
Using  Launch as Interactive user facilitates the window to pop up
using the active Window-station ID of the interactive user.
If it's the launching user then the window-station ID is that of the
currently logged in user(interactive) and therefore you are not
able to see the window.

Aravind

sanhot@hotmail.com wrote in message <6rl2id$rps$1@nnrp1.dejanews.com>...
>Hi, I've developed a ATL EXE which instantiates an ActiveX control (thru
>IDispatch). I run this server thru different client machine, with no call
to
>CoInitialiseSecurity. Also, on my server m/c, for this particular server,
>I've turned on DCOM facility. I'm using CocreateinstanceEx for remote
>instantiation.
>
>If the client & server reside on same machine, I'm able to see the window
>generated by the server component. However, if the client is on another
>machine, I can see just the process in Task manager but not the window.
>
>What could be the solution of this problem? I have logged in using the same
>user/password on both the machines. (both NT workstation 4.0 sp3) Since the
>server component creates timer object, it is imperative for it to create a
>window of its own.I would be glad to know the solution and any help
pointers
>on this topic.
>
>Thanks in advance,
>Sanjay
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum
>