Looking at your message, Steve, triggers something in my mind. Does connecting back to the first DB take a long time?
If not then: Does the second DB have an owner password? If so then: Try connecting to the problem db and set the user to the owner. At the R> issue the command REVOKE ALL PRIV FROM NONE Now change the user back to some other name. I had this problem at another client, was caused by literally thousands of bogus privileges being generated. Could never figure out how they were being created, but putting this command in the code that connects to the DB will keep it clean from now on. The junk grows relatively slowly so you should never see a problem again. The slowness is caused by megabytes of network traffic when the data dictionary is read. Normally the network traffic for this is only a few KB. -- Dennis McGrath mailto:[EMAIL PROTECTED] -- Productivity Tools for R:Base Programmers http://www.enteract.com/~mcgrath/dennis -- Full time consultant with: SQL Resources Group Steve Hartmann Oak Park, IL mailto:[EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Stephen R. Hartmann Sent: Wednesday, December 05, 2001 10:41 PM To: [EMAIL PROTECTED] Subject: RBDOS - Server 2000 - Slow Connecting I know I have seen this talked about before, but I need to ask it again. I have a client who is running RBDOS and upgraded from Novell to Windows 2000 Server. Whenever a second user connects, the CONNECT command bogs down. It takes about 10 seconds to connect to a 600MB data base. This would not be a big problem except the application has to connect to a second data base when one of the menu selections is made. I was able to solve most of their problems but minimizing the number of time the data base is connected to, but I was hoping someone would have a solution that would eliminate the connect delay. Thanks Steve Hartmann ========================================= TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just the two words: UNSUBSCRIBE rbase-l ================================================ 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
