FreeCastle wrote: But anyway I have to put an Invalidate() into the OnSize handler, because without that I see the changes only after hiding and showing again the dialog. That's because only the new part of the window is invalidated (marked for repainting) during a resize. To force the entire window to be repainted when the size changes, invalidating on WM_SIZE is fine. FreeCastle wrote: I don't really understand why this has to be done by a HDC Why what needs to be done with an HDC? If you want to keep a Graphics object (associated with a HDC for the window) around for the life of the window then you may want to consider using CS_OWNDC in the window class. See the RegisterClass API for details (AfxRegisterClass for MFC). Mark "If you can dodge a wrench, you can dodge a ball."

Ah thank you a lot, the first link was very informative. That DisconnectEx function looks cute, but I think I'll avoid it because it only runs on XP or higher. I think I use shutdown, and if I understood that article right, I have also to "create" the socket (by a call to socket(...)) again, when I want to "reuse" it for a new connection.

Yes that's of course a possibility, which means that I parse out the spaces behind the real string by hand. But I wondered if there wasn't any other possibility or if I made something wrong when getting this value from the database. But it seems that I made it correctly... that's just strange... Anyway thank you

Hi, did you receive my email ?

Mh... I made a new project for my windows service and placed my real application code in there, and what shall I say.. it works perfectly. I just made some refactorings to my original windows service code... don't know why it works now. Anyway thank you for your help. I will remember that tip with the debugging.

Hey, thanks a lot. Now it's all clear to me. (sry for late reply)

Hey thanks a lot again. And you're right, I am writing in fact a little protocol :-)