>> We see things like this when using an ODBC database when recordsets >> are not properly closed. It usually takes an hour, but I can reliably >> reproduce the error. Could it be that those 3-4 computers are being >> used more than the others?
> No. These are just view clients. Like the arrival/departure screens at an >airport. There are 3 different lists that are being displayed on the >various computers. We aren't using any database components. The lists are >updated using TCP/IP. After doing some additional testing, it appears that the error appears to be related to the socket control. The crash seems to be occurring on the End Sub command on the DataAvailable method. Are there any gotchas I should be aware of when using the socket control? --Seth -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
