> Thanks for your thoughts. I agree that the server should serialize the i/o > requests, and, if it didn't, we'd be in a big mess. Can you help me > understand why a CONNECT following closely behind a DISCONNECT would > fail? It doesn't wait to fail, it fails immediately. This has got to have > something to do with the conversation between R:Base and the OS, and the > only way I can understand it is that the OS cannot keep up.
Sorry Emmit, I don't have an answer. There is clearly something weird going on with shared file access where the file resides on Windows 2000. I did a fairly exhaustive search on GOOGLE a few months back, and found an occasional report of similar problems with both Foxpro and Access, so it seems to be a general shared file issue when Win2K is the server. If you run diagnostics, you will see that, with two different workstations opening a file that resides on a Win2K machine, that the network traffic for every file request increases by a factor of something like 500 times (not 500 percent, 500 times). This in turn makes R:Base appear to run about 10 times slower than usual. It is possible that something is set on your server, client, or in R:Base that will not allow CONNECT to use more than a certain amount of time. In that case, you may be timing out in some way. Only a guess. The next two things to look at would be getting a high level Win 2K expert to look at the Win2K machine setup, particularly with respect to file caching and, if that doesn't work, to actually hook up a packet sniffer and try to find out what all that extra network traffic is. -- Larry _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
