Hi Jordan,

>We create Electronic Cash Server (ECR) for our super markets application. All >Cash registers have interface module and communicate with server computer >through Serial port using MSComm control. This ECR Server communicates with >VFP application, which manages database operations, through WinSock control. >That was the reason to try to use Winsock ActiveX control to make TCP/IP >communication.

Right, but why don't you use TCP/IP between the cash register and the ECR server ? (Perhaps the cash register is not PC based ?)

>MS Winsock is VB ActiveX and work without any problems in VB, because it >allowed Method and Events with the same names. In VFP this is forbidden We >create as I explained in previous e-mail VB wrapper that avoid VFP >restrictions.

Which VFP restrictions ?

>In reality this is the same MS Winsock control (with the same features, >possibilities and restrictions, which are well explained in MSDN Help and >articles), but wrapped.

You're talking about Listen function and the backlog (=5) parameter (which limit the usage of Ms Winsock OCX)

int listen(
SOCKET s,
int backlog
);


>We distribute it as a OCX. It works with Winsock2.0. You can use MSDN help
Fine, how could I test it ?

Sincerely,
Roman