Jan,
I have seen the discussions you mentioned on this list before. The only reason I bring it up again is because my data was all messed up, due mostly (I hope) to the server problems we have had. If I am to use the ZERO ON, you are saying it would be wise to use also EQNULL ON? As a part time programmer, this is where I have a hard time "projecting" the consequences of the two scenarios. Jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Thursday, June 24, 2010 11:32 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: CFG file Jim, I can only speak for myself and really can't make any recommendations on this setting. In my case I run with these 2 settings. SET ZERO ON SET EQNULL ON They have kept me out of the most trouble. However I'm sure that this will spark some dialog (disagreement) on this list. Jan -----Original Message----- From: "Jim Belisle" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 24 Jun 2010 11:19:29 -0500 Subject: [RBASE-L] - Re: CFG file Jan, I sure do appreciate your help. I do use a form instead of an application, mostly because Razzak helped me understand some of the 7.6 functions by implementing them into a form. I do have some ON CONNECT options, just not ALL the settings. I do need to create an actual application some day. That is quite hard to do when programming is part time. Is it true that having the ZERO setting OFF is the best way to go? We have many NULLS in our Quote entry, order entry processes, mostly because our users click in and out of only fields they need. As I said earlier, I just want the database information to be consistent and the speed to be the best. Jim ________________________________ From: [email protected] [mailto: [email protected]] On Behalf Of jan johansen Sent: Thursday, June 24, 2010 10:57 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: CFG file Jim, I use the phrase from Highlander - "there can only be one". In my situation (I use the compiler) the CFG lives in only one place, the shared server drive. However critical database settings I can think of a couple of things I have done in the past. 1. Explore the ON CONNECT options. You can run a command file. 2. If you are using a form as a main menu, make a custom form action that has all the database settings that is called every time you connect i.e. PROPERTY RBASE_FORM_ACTION DbSettings "" in the form action we place the needed settings as such --Required settings for database SET ANSI OFF SET BELL OFF SET ROWLOCKS ON SET QUOTES=NULL SET QUOTES=" SET DELIMIT=NULL SET DELIMIT=, SET LINEEND=NULL SET LINEEND=รพ SET SEMI=NULL SET SEMI=; SET PLUS=NULL SET PLUS="+" SET SINGLE=NULL SET SINGLE="?" SET MANY=NULL SET MANY="*" SET IDQUOTES=NULL SET IDQUOTES="`" SET CURRENCY "$" PREF 2 B SET CASE OFF SET AUTOSKIP OFF SET REVERSE ON SET NULL -0- SET TOLERANCE 0. SET ZERO ON SET TIME SEQUENCE HHMMSS SET TIME FORMAT HH:MM:SS SET DATE SEQUENCE MMDDYYYY SET DATE FORMAT MM/DD/YYYY SET DATE YEAR 30 SET DATE CENTURY 19 RETURN Good luck, Jan -----Original Message----- From: "Jim Belisle" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 24 Jun 2010 10:32:46 -0500 Subject: [RBASE-L] - CFG file As is suggested, I always do my RELOAD on my local C drive. Because of that, I have a CFG file on the C drive and a CFG file on the G drive where the database is located. If these two CFG files happen to be different, will my session from my computer use the C drive CFG file instead of the G drive CFG? I ask this question because of this: We have had server problems lately that created problems with the database. The only way I was able to get the database back to being healthy, was to play with the ZERO setting in the CFG file. After the RELOAD last night, and after transferring my database back to the G drive, my ZERO setting was OFF which I believe is the setting suggested and the one I wanted. This morning upon connecting, the ZERO setting is now ON. What should I do? I just don't inconsistencies with my data. Jim
