G'day Emmitt, We currently have two threads running concurrently on the list, (glad the list can handle it, 'cos Windows doesn't seem to be able to handle sequential requests if they occur too quickly) both relating to an apparent inability of the Windows\R:BASE combination to handle actions at high speed.
One is yours on DISCONNECT\CONNECT, the other is James Bowyer's on a user clicking too quickly on a form button and trashing the R:BASE session. I don't know if there is a connection between the two... but if there is a link it may help the R:Team to isolate the cause. G'day James, I have been meaning to post a reply to your original post but haven't gotten to it until now. I too, have observed the accursed crashing on quick clicking on my machines. Most noticably on a form that contains three fairly large clickable images. Can happen first time accessing that form straight after starting an R:BASE session or after being in for some time, so it does not appear to be related to consumed memory not being released. At 08:15 AM 14/12/2001 -0500, you wrote: >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. Under >what conditions will R:Base fail to CONNECT (given that the path, shares, >rights, all that stuff is corrrect)? Warmest regards, Tom Grimshaw coy: Just For You Software tel: 612 9552 3311 fax: 612 9566 2164 mobile: 0414 675 903 post: PO Box 470 Glebe NSW 2037 Australia street: 3/66 Wentworth Park Rd Glebe NSW 2037 email: [EMAIL PROTECTED] web: www.just4usoftware.com.au This email and any files transmitted with it are confidential to the intended recipient and may be privileged. If you have received this email inadvertently or you are not the intended recipient, you may not disseminate, distribute, copy or in any way rely on it. Further, you should notify the sender immediately and delete the email from your computer. Whilst we have taken precautions to alert us to the presence of computer viruses, we cannot guarantee that this email and any files transmitted with it are free from such viruses. ================================================ 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
