I was asked yesterday, why I can't set a textbox to Null
me.textbox = Null

My reply was because it is a object and textbox is a properity?

and that I didn't really know for sure...

What is the correct answer?

If you try to run this code....

Text1.Text = Null

....you'll get an Error 94, Invalid Use of Null. The msgbox will contain a
Help button. Clicking that brings you to a page that says....

"Null is a Variant subtype used to indicate that a data item contains no
valid data."

The way I read it is.... you can't set a textbox's Text property = no valid
data.

The default property of a textbox control is .Text which is a string so what
you are trying to do is
me.textbox.text = Null

A string can not be "Null" so the assignment will fail.  You can assign a
zero-length string
me.textbox.text = ""
or you can use the vbNullString constant (it's technically a misuse of the
constant but VB will accept it) but that will be treated the same as the
zero-length string

Why, technically,  is this the case?  I thought you should use constants in
place of popular strings when ever possible.

Cheers
Stu

You should, but vbNullstring is *not* the same as "" and is doumented as
being defined for use in calling external rocedures that need a Null pointer
instead of a zero-length string.  The fact that it ends up accomplishing the
same thing inside VB is a side-effect of the way it was implemented.

Had MS ever made a VB7 they would have been free to change that and code
that relied on it would stop working because it relied on undocumented,
unsupported techniques.  Since VB has died with VB6 it's a moot point.

Fuzzy Logic
Is VB6 still alive and well?
True = -1 ?
Opening eml files.
Nested loop limit