I would not keep the DB in the same directory w/ the EXEs. Make your EXE directory read only. Users have to have R/W access to the database files.
You might want to put each of your database in a directory by itself. I like to keep my applications seperated. If I have one application that has a bunch of command files and uses a couple of database, I put that all in one directory. I can then set security at the directory level. Do your security with the Novell groups, and then you just need to add the users to the groups to give them all the access they need. You don't want to have to keep track of every users access. Troy ===== Original Message from [EMAIL PROTECTED] at 10/11/02 2:39 pm >Troy, Emmit > >I guess I need to brush up some more on setting rights. >The problem I have is I have a least 3 different sets of users >with different rights. One that has full rights on the directory, >one that has rights just on a couple of databases, and another >that has rights on about 30% or so of the db's ... With the >db's in the same directory as the RBase's exe, I'm not sure >how to set the rights for different users/groups so some of them >don't ever see any of the Accounting are related db's.. > >Have to look into this more > >AND, ok... I will only reload after I figure out this rights >problem.. It sure would improve things around here. > >Thanks, >Jim Limburg > >--- Troy Sosamon <[EMAIL PROTECTED]> wrote: >> With a pack, the files will keep their rights. A reload creates new files >> so you would need new rights. I set the rights at the directory level so I >> don't need to worry about individaul files. >> >> The files sizes will not necessarly be the same between a pack and a reload. >> A reload will be more efficient than a pack. A reload rebuilds the >> database from scratch where a pack just moves stuff around in the same >> database. In this day and age of large inexpensive hard drives, there is >> no reason to ever do a pack. You might on occasion need to do a PACK KEYS, >> but my opinion is if you need to do that, you just as well reload the whole >> database. >> >> Troy Sosamon >> >> ===== Original Message from [EMAIL PROTECTED] at 10/11/02 1:22 pm >> >G-Day all >> > >> >Does anyone know off the top of their head if I run reload >> >on a database on a Netware network then will the files loose >> >their rights like files that are deleted. I say this cause >> >I know when I patched with latest Rbase beta patches that >> >replaced the RBG65.exe and so other files in the patch all >> >groups and users in netware lost their rights on these files. >> > >> >I didn't know if the same would occur during a reload or not >> >on netware.. Additional Info. I have a couple of senario's for >> >people running RBase.. I set up groups in netware and in these >> >groups I assign rights to all the files needed to run rbase on >> >network. I assign other rights like databases and such (which >> >are all in the same dir as the rbase executeable) in another group >> >so it's easier to manage (mabye?). The one hassle is just what I >> >am talking about, when I kill a file the rights have to be reassigned. >> > >> > >> >Another question.. it seems to me that persons on this list and >> >what I have read in the Syntax that there should be no differences >> >between the rb? file sizes whether a reload or pack is issued. I >> >ran a reload on a local database and the files sizes never changed. >> >I then out of curiosity ran a pack and the files did shrink some.. >> >Am I crazy? - don't go into to much detail - ha,ha. I'm using >> >RBase DOS65 842_RT03 >> > >> >Thanks >> >Jim Limburg >> > >> >__________________________________________________ >> >Do you Yahoo!? >> >Faith Hill - Exclusive Performances, Videos & More >> >http://faith.yahoo.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/ > > >__________________________________________________ >Do you Yahoo!? >Faith Hill - Exclusive Performances, Videos & More >http://faith.yahoo.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/
