Buddy, Interesing idea! I will consider that option.
Jan -----Original Message----- From: "Walker, Buddy" <[EMAIL PROTECTED]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 28 Aug 2008 12:59:46 -0400 Subject: [RBASE-L] - RE: Second connection Jan What I do when I don’t want to chance anyone connecting to the database is I rename it. Then when I’m done I rename it back to the original name. RENAME OrigData.RB? TO MyData.RB? Buddy From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of jan johansen Sent: Thursday, August 28, 2008 12:54 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Second connection Group, I have a process that archives from one database to the another. I have a step that checks for the number of connections before I start the process. However the process can take 10-15 minutes and it never fails, someone will connect to either of the databases in the middle of the processes. Although I use SET MULTI OFF, when I disconnect from database 1 and connect to database 2, database 1 becomes available for connections because I am now in database 2. Anyone have any slick tricks to open a second connection with code so that with SET MULTI OFF I have the only connections allowed to the database and then shut down both connections after I am done? Jan
