[AccessD] An Interesting question

It spontaneously becomes not null!
Yea!

-
Michael R Mattys
MapPoint and Database Dev
www.mattysconsulting.com

-
----- Original Message ----- 
From: "Rocky Smolin at Beach Access Software" <rockysmolin at bchacc.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Sunday, March 29, 2009 7:55 PM
Subject: Re: [AccessD] An Interesting question


> Quantum programming?  You don't know the value until you observe it?
>
>
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
> www.bchacc.com
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
> Sent: Sunday, March 29, 2009 4:43 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] An Interesting question
>
> Yes! of course it would, it couldn't be false because you don't know if it
> is true or false. You don't know anything.
>
> most excellent point stuart. :)
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart McLachlan
> Sent: Monday, 30 March 2009 10:35 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] An Interesting question
>
>
> Incorrect. Null = Null doesn't return False, it returns Null
>
>
> On 30 Mar 2009 at 10:27, Darryl Collins wrote:
>
>> My understanding of NULL, in the database sense is that it is unknown.
>>  It maybe a value or it may not be, you don't know what it is.  That
>> is why if you say NULL = NULL would return false, rather than true,
>> because you don't know what NULL is.