Thanks Bill, and everyone else responding to this thread. We're getting closer, but not quite there yet.
What seems to be happening is this: let's say there are three users connected to the db, users A, B and C. B changes a setting, lets say Zero=off. None of them disconnect, all three are connected while a new user, D connects too. User D picks up the user B setting of Zero=off as soon as he connects, which is wrong. This is regardless of his rbase.cfg setting because Zero is a DB setting. So, when does the DB settings of user B actually get written to the DB? I'm saying it's not only if he is the last user to disconnect, as Bill stated. I think it is as soon as he interacts in any way with the DB! Otherwise, user D wouldn't have a problem because there were always other people connected. If he (user D) initiated Bill's SETCONN.RMD as below, he would be fine as well, all settings intact and correct. However ..... Oterro users! What do we do about them? Is there a way to force the SETCONN.RMD to be run upon ALL connects so their settings are always correct? (Oterro is accessing the DB through a vb application doing connects and disconnects as needed.) Can the On Connect command be incorporated into this maybe? Hmmm.... Chuck Lockwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LockData Technologies, Inc. 309 Main Avenue, Hawley, Pa 18428 570-226-7340 ~ Fax: 570-226-7341 [EMAIL PROTECTED] ~ www.lockdata.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Downall Sent: Wednesday, August 09, 2006 2:29 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Rbase 6.1 DB settings in Multi-user environment Hi, Chuck, In the absence of an owner password, the last connection to let go of the database leaves behind its settings in the database, for all those settings that are saved with the database. That's at the point where the number of connections goes from 1 to zero. For that reason, I use two files SETDISC.RMD and SETCONN.RMD. SETDISC sets everything that should be done before the database is connected, so that this user will have compatible settings, esp. for multiuser. SETCONN has everything that should be re-established right after the connection, for example just in case some Canadian changed the date format to DD/MM/YYYY and was the last one to exit the database. All the character settings, date settings, NULL settings, etc. are critical here. For users who exit normally, you can also run SETCONN again just before the DISCONNECT or EXIT command, but that doesn't account for the abnormal terminations of R:BASE. So you must always run it right after CONNECT. Bill Chuck Lockwood wrote: > Bernie, > > The application changes a few of them temporarily, then changes them right > back. For example, to print collection letters, Zero is set off for > formatting purposes, then set back on less then a minute later. However, if > someone adds a record during that period, the computed column that tolals > the $$ amounts becomes null because there is posibly a null in one of the > columns being added. > > We got around this for years by setting a DB owner and granting permissions > explicitly to tables for other users. By doing this, the setting being > changed by one user do not effect anyone else. > > The reason behind the change is the client has found the DB to be more > stable when the .RB1 file is kept simple, no table comments, no grants, etc. > It is a busy application that historically experiences sporatic .RB1 > corruption. They have found that it is much more stable without granting > table access explicitly, but this is coming at the price of the erronious > setting issues. > > Thanks, > > Chuck Lockwood > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > LockData Technologies, Inc. > 309 Main Avenue, Hawley, Pa 18428 > 570-226-7340 ~ Fax: 570-226-7341 > [EMAIL PROTECTED] ~ www.lockdata.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Lis > Sent: Monday, August 07, 2006 8:07 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Rbase 6.1 DB settings in Multi-user environment > > Chuck, > Put these settings into your startup program. > If they do get changed, they will change back when anyone restarts. > How can anyone change them? Do you allow your users to get to the R> ? > Bernie Lis > ----- Original Message ----- > From: "Chuck Lockwood" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Monday, August 07, 2006 6:54 PM > Subject: [RBASE-L] - Rbase 6.1 DB settings in Multi-user environment > > >> Is there a way to prevent the DB setting below from globally being changed >> other then setting an owner of the database? I'm looking for something >> like >> the STATICDB setting that prevents table changes. >> >> If I do need to set the owner, is there a way to GRANT all table >> privileges >> to a user explicitly without specifying them table by table? >> >> These are the special character and operating condition settings are >> stored >> in a database. >> . AUTOSKIP >> . BELL >> . BLANK >> . CASE >> . CURRENCY >> . DATE >> . DELIMIT >> . IDQUOTES >> . LINEEND >> . MANY >> . NULL >> . PLUS >> . QUOTES >> . REVERSE >> . SEMI >> . SINGLE >> . TIME >> . TOLERANCE >> . ZERO >> >> Thanks, >> >> Chuck Lockwood >> >> --- RBASE-L >> ================================================ >> TO POST A MESSAGE TO ALL MEMBERS: >> Send a plain text email to [email protected] >> >> (Don't use any of these words as your Subject: >> INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, >> REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) >> ================================================ >> TO SEE MESSAGE POSTING GUIDELINES: >> Send a plain text email to [email protected] >> In the message SUBJECT, put just one word: INTRO >> ================================================ >> TO UNSUBSCRIBE: >> Send a plain text email to [email protected] >> In the message SUBJECT, put just one word: UNSUBSCRIBE >> ================================================ >> TO SEARCH ARCHIVES: >> Send a plain text email to [email protected] >> In the message SUBJECT, put just one word: SEARCH-n >> (where n is the number of days). In the message body, >> place any >> text to search for. >> ================================================ >> >> > > --- RBASE-L > ================================================ > TO POST A MESSAGE TO ALL MEMBERS: > Send a plain text email to [email protected] > > (Don't use any of these words as your Subject: > INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, > REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [email protected] > In the message SUBJECT, put just one word: INTRO > ================================================ > TO UNSUBSCRIBE: > Send a plain text email to [email protected] > In the message SUBJECT, put just one word: UNSUBSCRIBE > ================================================ > TO SEARCH ARCHIVES: > Send a plain text email to [email protected] > In the message SUBJECT, put just one word: SEARCH-n > (where n is the number of days). In the message body, > place any > text to search for. > ================================================ > > >
