I KNOW we have rehashed this a dozen times but how about
one more time?I'm about to go live on a DOS-to-Windows conversion (up to date version of RBWin) on a W2K network with Win98 workstations. Their current 6.5+ DOS just flies and has never had any problems under this network. The speed is great and I've never had memory leakage problems. In the testing phase of RBWin, they're all complaining about how slow everything is. Of course, the one initial CONNECT takes about 5 seconds. There's a form based on a 1-row dummy table that can take 10 seconds to load. The application flies on a local drive. Again the main user form is brought up based on a primary key search, same thing -- can take 10 seconds to come up. Immediate if it's local. I went back and reread all the email I've been saving about this topic. There's no App.Exp so there's no extra connects around. I read about tweaking Norton AV settings (which I know they have) and will do that. I also read about a possible 'time out' fix (Net Config Server /autodisconnect:-1) so will try that too. Any other tips that people have found lately? Their network guys support other RBase clients, so are familiar with the product, and they point their fingers back at us. Karen ================================================ 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 ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
