home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!ogicse!sequent!muncher.sequent.com!krader
- From: krader@sequent.com (Kurtis D. Rader)
- Newsgroups: comp.os.ms-windows.apps
- Subject: Re: ACCESS: computations with blank fields
- Message-ID: <1993Jan26.011806.3264@sequent.com>
- Date: 26 Jan 93 01:18:06 GMT
- Article-I.D.: sequent.1993Jan26.011806.3264
- References: <1993Jan25.194751.2567@tijc02.uucp> <1k1q6fINN5n7@transfer.stratus.com>
- Sender: usenet@sequent.com (usenet )
- Distribution: usa
- Organization: Sequent Computer Systems, Inc.
- Lines: 23
- Nntp-Posting-Host: crg8.sequent.com
-
- rscott@vineland.pubs.stratus.com (Richard Scott) writes:
- >In article <1993Jan25.194751.2567@tijc02.uucp> kjf388@tijc02.uucp (Ken Fisher
- >) writes:
- >> On-line help says the "sum" function interprets blanks as zero, but that
- >> does not seem to be the case.
- >Yes, the Sum function (as in 'Sum(x)') does interpret Null values (blanks) as
- >zero. But the expression operators (as in '+'), do not. In expressions, binary
- >operators with either or both operands Null yield a Null result. I ran into
- >the same problem and was able to get around it only by writing functions (e.g.,
- >NonNullDifference(x,y) in Access BASIC.
- >-----
- >Richard Scott
-
- The best advice I can give is DON'T USE NULLS if you wish to retain your
- sanity and have any hope of trusting the output of your queries. See
- chapter 8 of "Relational Database Writings 1985-1989" by C. J. Date.
- He has also written a several essays since that time on this topic which
- have appeared in various magazines.
- --
- Kurtis D. Rader, Technical Support Engineer voice: 800/854-9969
- NAOTS, Sequent Computer Systems fax: 503/578-5453
- 15450 SW Koll Parkway, M/S WIL1-501 UUCP: ...uunet!sequent!krader
- Beaverton, OR 97006-6063 internet: krader@sequent.com
-