Ah I see. At one of the conferences, I think I remember someone's maintenance routine where they placed a dummy file in the database directory when they didn't want anyone to connect to the db, and deleted it when they were done. So you could do something like that: At the beginning of your process, write some file to the database directory. In the rbase.dat file for the users (or other startup file), before attempting to connect, check for the file. If it's there, give the user a message that the db is currently unavailable due to maintenance. Then at the end of your process, when you're done with both dbs, remove the files.
Dawn
-------------- Original message from "jan johansen" <[EMAIL PROTECTED]>: --------------
Dawn,Good thought. However I have battled with this database because the settings willnot allow sconnect and sattach. The owner of the database is adamant that wenot touch those settings so I am stuck with them.Jan
-----Original Message-----
From: "Dawn Hast" <[EMAIL PROTECTED]>
To: [email protected] (RBASE-L Mailing List)
Date: Thu, 28 Aug 2008 16:57:47 +0000
Subject: [RBASE-L] - Re: Second connection
Can you sconnect to the second db and sattach the necessary tables to update?-------------- Original message from "jan johansen" <[EMAIL PROTECTED]>: --------------
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, someonewill 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 connectto database 2, database 1 becomes available for connections because I am nowin database 2.Anyone have any slick tricks to open a second connection with code so that withSET MULTI OFF I have the only connections allowed to the database and thenshut down both connections after I am done?Jan
