First up, if both are running as separate processes then nothing is in the "same space" as such.
It's been a long time since I did any detailed COM work so I'm a bit rusty, but I think the key to this will be the threading and instancing model your COM server is employing in the A process and re-entrancy issues in the A process. -----Original Message----- From: delphi-boun...@delphi.org.nz [mailto:delphi-boun...@delphi.org.nz] On Behalf Of Robert Martin Sent: Friday, 3 June 2011 12:06 To: NZ Borland Developers Group - Delphi List Subject: [DUG] COM issue Hi I have app A that runs (using create process) app B. App B at one point tries to use COM to access app A. This freezes. When app B is run manually it works fine. I assume this has something to do with B running in the same 'space' as A. I have tried CreateProcess(Nil, pChar(appName + ' AUTORUN'), nil, nil, false, DETACHED_PROCESS + NORMAL_PRIORITY_CLASS, nil, nil, startinfo, proc_info) <> False) But to no avail. Any suggestions? Thanks Rob _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: delphi@delphi.org.nz Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to delphi-requ...@delphi.org.nz with Subject: unsubscribe _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: delphi@delphi.org.nz Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to delphi-requ...@delphi.org.nz with Subject: unsubscribe
