Subject Re: SUM From Andy Taylor <andy.taylor.1959@outlook.com> Date Mon, 15 Jan 2024 18:54:10 +0000 Newsgroups dbase.getting-started Hi Ronnie, That's why I said it's a preference. To expand on that slightly I prefer boolean logic with only two states, it's reliable that way. For a state with three or more alternatives I would not use a boolean field. However, I am aware that my opinion is probably a minority one. I did not mean to imply that the default setting should be the other way around... although reading my post again it could be taken that way. Ooops instead of Eeek. :-) Regards, Andy > In article <JohWGBuRaHA.1876@ip-AC1E04A7>, andy.taylor.1959@outlook.com > says... > >> Eeek! It's a matter of preference, but I try to avoid nulls as much as >> possible. > > A matter of preference yes, but also one of data accuracy and integrity. > > Consider a simple boolean field labelled "COVID Vaccinated". > > You cannot default to "No" or "False", because that may not be true. > > There are actually three valid data states for this boolean field. > > True / Yes - We know with certainty the individual is vaccinated. > > False / No - We know with certainty the individual is NOT vaccinated. > > Null / Unknown - We don't know whether they are vaccinated or not. > > >> "Set AutonullFields Off" and "xxx.rowset.autonullfields=false" >> are my friends here and neither are the default settings in dBASE. >   > And neither should they be !!! . . . . . >