Ok Here is the problem. I have an Old C program that talks to an even older NPL program. Ok now the C functions can be exposed to the NPL program for use so that a coder in NPL can run a C function. Ok now the C DLL loads up with the NPL program. Ok Now I need the C program to send a message to a VB form or an activeX control on a vb form. then wait for a message to return once returned it will send a message back to the NPL. I got the C to NPL covered I just need C to VB. Now I have tried Winsock but for some reason the way I have to do it in C doesn't like working with the Winsock activeX control in VB so If I do it low level with the winsock API in VB it ends up taking 100 percent of resources while it waites. Now I got it to work and make a connection but not to receive it. It seems that it breakes the connection right after it connects. Now if I do a server in C++ in cosole mode it seems to work fine it opens a dos window and runs and waites and receives the message and resets. No problem. If not winsock maybe something else. There's nothing worse then retro fitting. Let me know what you think and how much.
## Deliverables
Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. Complete copyrights to all work purchased.
## Deadline information
need in a couple weeks.