>Roman,
>If I understand you correctly (correct me if I'm wrong)
>
>>It's work fine, is-it possible to share with the child process the parent object environment and to "BINDS" some event of the parent object ?
>>
>
>to bind event you could try use CreateEvent and SetEvent in the parent process and then OpenEvent in the child process. I think www.news2news.com has the example for this
>

There's a full implementation of the Windows Event object in ClsEvent, available in the Downloads section here on UT. Be aware that events are synchronization objects and not data transfer objects; you need to provide a means to either expose the heap of one process to another or to perform some sort of IPC to transfer data.

The clipboard is probably the simplest IPC mechanism to use, but it isn't exclusive or name-able; the same clipboard is shared amongst all processes, so that someone running Word who copies a block of text will stomp on whatever was previously there. Windows messages, named pipes and memory-mapped file I/O are all available IPC mechanisms that can be controlled closely and perform very well; Windows messages submit message packets to a Window or thread message queue, named pipes are two-way asynchronous links between two processes that can be used to queue up streams of data, and memory-mapped file I/O creates a shared memory block of upto 64K in each process that has the memory-mapped file open; what's written in one process' block of the file is readable (and writable) from another process addressing the same 64K block of the mapped file.