Karen I was using NAME before netuser was available. I also kept the rbase.exe file on a network drive. That is why I only had one cfg and dat file to control. Different users had different access to menu items and tables. Then when netuser came about I just set the name to it and continued using NAME.
Buddy From: 'Karen Tellef' via RBASE-L <rbase-l@googlegroups.com> Sent: Monday, January 31, 2022 9:00 AM To: rbase-l@googlegroups.com Subject: Re: [RBASE-L] - Multi-User commands Best Practices Go ahead and flame me on this one, but I've had the same modus operandi ever since I think version 9.0 I don't use CFG files. Ever. Anywhere. I have no clue where/if they are installed, nor where they are. And to this day it has never presented a problem in any of my installations. To me it was one of the best enhancements ever, that you can basically ignore those CFG files if you want to. Need to add a user? Give them the desktop icon that points to the network RBase install and you're done. Do they have/need a CFG? I've never assigned one to a new user. I'm not sure how RBase handles it, but I don't care because it works wonderfully. 100% of my commands, like the ones you list Doug, are in the startup file. That way if you want to change anything, you change one program. You don't run around and change/copy over new CFG files for every user. I never use "name" anymore, I use NetUser. Karen -----Original Message----- From: Buddy Walker <walker.bu...@comcast.net <mailto:walker.bu...@comcast.net> > To: rbase-l@googlegroups.com <mailto:rbase-l@googlegroups.com> Sent: Mon, Jan 31, 2022 6:18 am Subject: RE: [RBASE-L] - Multi-User commands Best Practices Doug I would only put those in the cfg file. I would set the NAME in RBASE.DAT like this SET VAR vUserName = (CVAL(‘NETUSER’)) SET NAME &vUserName I would then make sure the RBASE.DAT AND rbase CFG file were located in same folder as the rbase EXE Make sure there aren’t any other RBASE.DAT and rbase CFG file located anywhere. Buddy From: rbase-l@googlegroups.com <mailto:rbase-l@googlegroups.com> <rbase-l@googlegroups.com <mailto:rbase-l@googlegroups.com> > On Behalf Of Doug Hamilton Sent: Sunday, January 30, 2022 10:32 PM To: R:Base List <rbase-l@googlegroups.com <mailto:rbase-l@googlegroups.com> > Subject: [RBASE-L] - Multi-User commands Best Practices In the recent R:Base Multi-User Guide, the recommended sequence for Multi-User Concurrency Settings in a startup file, e.g. RBASE.DAT, is: DISCONNECT SET MULTI ON SET STATICDB ON SET FASTLOCK ON SET PAGELOCK OFF SET ROWLOCKS ON SET VERIFY COLUMN SET WAIT 4 SET INTERVAL 5 The same settings are found in the .CFG file, e.g. RBENGINEX5E.CFG MULTI ON STATICDB ON FASTLOCK ON PAGELOCK OFF ROWLOCKS ON VERIFY COLUMN WAIT 4 INTERVAL 5 Is it correct that: 1) the CFG file is processed before the startup DAT file? 2) The order of the commands in the CFG should be the same as in the DAT file? 3) The SET commands in the DAT file are redundant and are not really necessary in the DAT file unless settings need to be changed for special circumstances? Note that the user Guide states: "The settings may be set within the R:BASE configuration file. However, the settings are best set in a startup file before connecting to the database. For example: ..." Why are the settings best set in a startup file? Shouldn't default settings be established in the CFG file and modified only if necessary? TIA, Doug _____ <https://www.avast.com/antivirus> This email has been checked for viruses by Avast antivirus software. www.avast.com <https://www.avast.com/antivirus> -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com <mailto:rbase-l+unsubscr...@googlegroups.com> . To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/f09f7740-a3a9-aebf-5c8d-963075b275c6%40wi.rr.com <https://groups.google.com/d/msgid/rbase-l/f09f7740-a3a9-aebf-5c8d-963075b275c6%40wi.rr.com?utm_medium=email&utm_source=footer> . -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com <mailto:rbase-l+unsubscr...@googlegroups.com> . To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/004901d8169c%24ad391c20%2407ab5460%24%40comcast.net <https://groups.google.com/d/msgid/rbase-l/004901d8169c%24ad391c20%2407ab5460%24%40comcast.net?utm_medium=email&utm_source=footer> . -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com <mailto:rbase-l+unsubscr...@googlegroups.com> . To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/480366446.3189550.1643637579601%40mail.yahoo.com <https://groups.google.com/d/msgid/rbase-l/480366446.3189550.1643637579601%40mail.yahoo.com?utm_medium=email&utm_source=footer> . -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/003601d816c2%244a4238b0%24dec6aa10%24%40comcast.net.
