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.
================================================

Reply via email to