The NAME from the rbase.cfg file should be unique for each user. Everyone should have their own rbase.cfg file with a differnt name.
Assuming you have issued a grant statement or defined an owner password, the USER is the user name or aka password that is being used to access the database. There are lots of different ways to control this security depending on your users and applications. You can have groups of different people accessing the system that use the same USER name, but tye should all have different 'NAME's in the rbase.cfg file. Troy ===== Original Message from [EMAIL PROTECTED] at 10/14/02 5:14 pm >Just checking back on a few posts and nobody made any comment on this one - >any ideas anyone? > >Thanks & regards, >Alastair. > >----- Original Message ----- >From: "Alastair Burr" <[EMAIL PROTECTED]> >To: "R:Base ListServer" <[EMAIL PROTECTED]> >Sent: Monday, September 16, 2002 2:39 PM >Subject: User Name / Network ID / Password / CFG File > > >> Hi all, I'm confused - nothing new there, I hear you all mumble <g>: >> >> Could somebody please explain - as simply as possible - the relationship >> between these R:Base "names": >> >> NAME in the RBASE.CFG file - which seems to return NETWORK NAME with SHOW >> NAME >> >> USER which seems to return USER ID with SHOW USER >> >> OWNER NAME which doesn't seem to need a password. For instance: >> CREATE SCHEMA AUTHOR DBNAME OWNER_NAME >> >> seems to use OWNER_NAME as a password so that _if_ that name is secret the >> DB is secure. >> >> >> In the past, before SET USER had a password option, the user name was, >> effectively, the password. But now in a Multi-User situation does every >USER >> ID have to be different even if the NETWORK NAME is different? >> >> In other words, can a group of users have a single user name without >having >> separate passwords and more than one gain access to the same database? >> >> If so, what name, if any should go in the single RBASE.CFG file? >> >> >> This is following on from Razzak's reply to JM Gratias on 30/05/2002 about >> running two copies of R:Base on a single PC. All that appears to be >> different in Razzak's method is the SET NAME command before the >application >> is run so, it seems to me, that if I have a login system that knows my >USER >> ID then I ought to be able to SET NAME based on that knowledge and run as >> many copies of R:Base as the PC can handle with different users. >> >> Currently this fails with one user getting access and the other failing >with >> an error message about the database being in single user mode even though >> multi is set to on. I suspect that this is due to the same user id being >> used for both sessions. However, I want owner access in both cases... >> >> Thanks in advance for any light that anyone can shed, >> Regards, >> Alastair. >> >> ---------------------------------- >> A D B Burr, >> St. Albans, UK. >> ---------------------------------- >> [EMAIL PROTECTED] >> ---------------------------------- >> >> ================================================ >> 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 >> ================================================ >> TO SEARCH ARCHIVES: >> http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >================================================ >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 >================================================ >TO SEARCH ARCHIVES: >http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ 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 ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
