Need NSBasic WinSock Recommendations and Advice(repost)

Hello Dear Coder: I am looking for a programmer experienced with Pocket PC development, specifically using NSBasic (similar to eVB, AppForge). I need help making my Pocket PC app communicate with my regular windows app using TCP, specifically IPWorks component (a more advanced version of Winsock). I am a VB programmer who decided to add PocketPC (and hopefully Palm) versions to my existing software. I only have 48 hours of experience in NSBasic and already have an issue that I cannot solve myself. I am creating a Pocket PC Client for my time clock software. The Server is a VB app with a Winsock OCX. I thought that I could just replicate my existing VB code that I used in the Client. But, I cannot get my PPC app to communicate reliably. Based on advice from NSBasic user group and web site, I have almost immediately stopped using the Winsock that comes with NSBasic and switched to IPWorks (V5 ActiveX 5.0.1284 Edition for Pocket PC 2000 Trial Version). Just like others were saying, the Winsock that comes with NSBasic often only sends 1 character they I do a SendData. Not good :( But, when using IPWorks, I see that in 70% of cases, my VB Server doesn't receive anything. My NSB code is attached. Is this because I am using Microsoft's emulator for my tests and the networking is not being emulated properly or is there another reason? Can you code a reliable communication sample for me with retries, failsafes or any other mechanisms that would insure that what I am sending will get to the Server? Will be waiting for your reply, Eugene ## Deliverables Reliable Winsock (IPWorks) communication code for Pocket PC ## Platform Pocket PC