NiceArse
October 17th, 2000, 05:42 AM
Im relativly new to COM so go easy:)
I've got a COM Server(Out of Process) that is used by two applications,
My problem is I need to let the server start a new process BUT under Win2k and Win98 this new processes Windows are started in the BackGround.
The question: Is there anyway around Win2ks new trick of blocking all but the CurrentWindow and Children OR Can the COM Process be made a child of the main process when its called.
This needs to work on 2k + 98 so AllowSetForegroundWindow() is out of the question. and I can't alter the calling application.
Any help would be greatly appreciated.
I've got a COM Server(Out of Process) that is used by two applications,
My problem is I need to let the server start a new process BUT under Win2k and Win98 this new processes Windows are started in the BackGround.
The question: Is there anyway around Win2ks new trick of blocking all but the CurrentWindow and Children OR Can the COM Process be made a child of the main process when its called.
This needs to work on 2k + 98 so AllowSetForegroundWindow() is out of the question. and I can't alter the calling application.
Any help would be greatly appreciated.