Code Comments
Programming Forum and web based access to our favorite programming groups.Hello everyone, I have catch-22 dilemma and need your kind help, again. I made a simple graphical window program I will call "Parent", the parent will launch a console-window (characterBase) program I will call "child", by using the win32 API "CreateProcess" function, and will Wait for this program INFINITELY by using the win32 API function "WaitForSingleObject", until it returns control back to the parent. the child needs to send a message to the parent during its active execution time and request a service operation, for example: (generate & sort a text file, or launch a GUI-Graphical Program). however, when the child is active --- the parent is hibernating in the background in its waiting-state, until it receives the return code from the child program along with the returned OS control. My Dilemma? how can I wakeup the parent to respond to the message it will receive from the child while keeping the status quo?? the workaround is for the child to exit with a special ReturnCode, and have the parent respond to that request accordingly, and then the parent would Re-Launch back again the child program so it can continue its Previous Process --- however, when the child gets Re-Launched, the end-user will not be able to pickup from where he or she leftoff the last operation with the child. Also, Only the parent program is capabl of launching a Graphical Window program by using the win32 API "CreateProcess" function. I am hoping that you have a wakeup call for cobol or me. thanks a lot for the generous help, Kellie.
Post Follow-up to this messagePowered by vBulletin
Copyright 2000-2006 Jelsoft Enterprises Limited.