Last night, I discovered something:
MyRecordSet.Field("Age") = NULL
MyRecordSet.Update
If IsNull(MyRecordSet.Field("Age")) Then
MsgBox "It worked!"
Else
MsgBox "It didn't work. Dang!."
End If
The second pithy message box always pops up. The IsNull always returns
false. However, the Database does contain a Null! That's great, or at
least less sucky than when I thought it wasn't working at all. Now my
program works, it just doesn't know it.
It's like the Value property of the Field object gets filled with some
value (possibly Empty or Nothing) that VB doesn't recognize as a Null,
even though a Null is inserted into the database. When I hover above
the field (in debug mode), no ToolTip appears to show me a value. When
I hover over any other field, the value is displayed in a ToolTip.
When I hover over a field that is recognized as Null (with IsNull) a
ToolTip with the word "Null" appears. When I hover over a field that
is recognized as Empty (with IsEmpty) a ToolTip with the word "Empty"
appears. When I hover over a field that is recognized as Nothing (with
Is Nothing) a ToolTip with the word "Nothing" appears.
This is something else, an anomaly. I wonder if I'm opening some
space/time vortex. I'm not sure, but I will research more. Perhaps I'm
mad to delve into these things, but I must know. My assistant is
obviously concerned, and scared...THE FOOL! Can't he see that we are
on the verge of one of the greatest programming discoveries of all
THEM ALL!!! They'll know I was right when I break through! I'm close!
I KNOW it!! I can FEEL it!!!!!
[Editor's note: This was the last log entry...the last known words of
Mr. White. As of today, his whereabouts are unknown.]
No, but seriously, has anyone ever seen this behavior before?
==================================
A. Scott White
Senior Systems Analyst
Affiliated Computer Services, Inc.
==================================