>>I will give a try at Brattberg and will keep you inform.
>
>Ok, here's what I have found so far.
>
>There is no event which mean we have to plug a timer and verify each second if we have new data coming from the server. But, it's workable.
>
>The connection timeout is the default winsock 3 minutes and there doesn't seem a way to adjust that. This is innacceptable as a failed connection will lock the application for 3 minutes until the control react.
>
>There is only 5 properties so I guess he plugged all the default for all other properties. This is not as flexible as other controls I have tested but it is ok so far.
>
>The control is dated from last August so I don't know if the development was stop and if other version will be available.
>
>I sent emails to the owner of the product. Will keep you inform.

Thanks for the info. Sounds like you are on a similar journey.

I looked at several controls so far as well.

BTW, what is the difference between an HTTP control and a sockets control?

I really do not want to get into buffering text back and forth do you? An alternative is to FTP files, but that of course supposedly is not as secure as sockets, unless of course you encrypt the files you are FTPing, which is in fact what I am doing at present...and in my mind is the same difference as secure sockets.

Off the record, what is needed is a ODBC-HTTP/Sockets type of control. Or better yet imagine going into the ODBC Administrator on the remote side and setting up a system data source name(DSN), description, and TCP/IP for the system to point to. The system to point to would of course be the server and have an ODBC compliant control built into/running waiting for calls from the remote, and then sending back results (viola client/server). I am sure this currently being worked out as we speak. Although everyone knows ODBC is a bottleneck.