Null date value

[Brad]

If I need to assign a NULL value to a date variable, how would I go about
doing that? For right now I am using 01-01-2001, however I don't want to use
a "real" date if the date should really be NULL.

Thanks for the information.

[Armin Zingler]

"Brad" <Br**@discussio ns.microsoft.co m> schrieb

If I need to assign a NULL value to a date variable, how would I go
about doing that? For right now I am using 01-01-2001, however I
don't want to use a "real" date if the date should really be NULL.

Thanks for the information.

Declare it as Object or use a 'WrappedDate' and assign Nothing to represent
Null.

Class WrappedDate
public Value as date
public sub New(value as date)
me.value =value
end sub
end class
Armin

[Herfried K. Wagner [MVP]]

"Brad" <Br**@discussio ns.microsoft.co m> schrieb:

If I need to assign a NULL value to a date variable, how would I go about
doing that? For right now I am using 01-01-2001, however I don't want to
use
a "real" date if the date should really be NULL.

See:

<URL:http://www.google.to/groups?threadm= %23wkAjb1mDHA.2 080%40TK2MSFTNG P10.phx.gbl>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[Oenone]

Brad wrote:

If I need to assign a NULL value to a date variable, how would I go
about doing that? For right now I am using 01-01-2001, however I
don't want to use a "real" date if the date should really be NULL.

I use Date.MinValue to represent a "null" date. This works very nicely.

--

(O) e n o n e

[Mythran]

"Oenone" <oe****@nowhere .com> wrote in message
news:NI******** ****@newsfe5-gui.ntli.net...

Brad wrote:

If I need to assign a NULL value to a date variable, how would I go
about doing that? For right now I am using 01-01-2001, however I
don't want to use a "real" date if the date should really be NULL.

I use Date.MinValue to represent a "null" date. This works very nicely.

--

(O) e n o n e

Unless your dealing with historical data and the MinValue of Date is the
same as a Date you really need to store in the field :)

Mythran

[Michael C#]

Hehe. Then use DateTime.MaxDat e and let the
great-great-great-great-great-great-great grandkids deal with the Y10K
problem.

"Mythran" <ki********@hot mail.comREMOVET RAIL> wrote in message
news:em******** *****@TK2MSFTNG P15.phx.gbl...

"Oenone" <oe****@nowhere .com> wrote in message
news:NI******** ****@newsfe5-gui.ntli.net...

Brad wrote:

If I need to assign a NULL value to a date variable, how would I go
about doing that? For right now I am using 01-01-2001, however I
don't want to use a "real" date if the date should really be NULL.

I use Date.MinValue to represent a "null" date. This works very nicely.

--

(O) e n o n e

Unless your dealing with historical data and the MinValue of Date is the
same as a Date you really need to store in the field :)

Mythran

[Mythran]

"Michael C#" <ho***@boutdat. com> wrote in message
news:eU******** ******@TK2MSFTN GP09.phx.gbl...

Hehe. Then use DateTime.MaxDat e and let the
great-great-great-great-great-great-great grandkids deal with the Y10K
problem.

"Mythran" <ki********@hot mail.comREMOVET RAIL> wrote in message
news:em******** *****@TK2MSFTNG P15.phx.gbl...

"Oenone" <oe****@nowhere .com> wrote in message
news:NI******** ****@newsfe5-gui.ntli.net...

Brad wrote:
If I need to assign a NULL value to a date variable, how would I go
about doing that? For right now I am using 01-01-2001, however I
don't want to use a "real" date if the date should really be NULL.

I use Date.MinValue to represent a "null" date. This works very nicely.

--

(O) e n o n e
Unless your dealing with historical data and the MinValue of Date is the
same as a Date you really need to store in the field :)

Mythran

Yeah...

Are you sure that January 1st, 9999 is far enough in the future though?
8-{p

Mythran

[Oenone]

Mythran wrote:

Are you sure that January 1st, 9999 is far enough in the future
though?

It had better be, or else your VB.NET app isn't going to be much use. :-)

--

(O) e n o n e

[Michael C#]

"Mythran" <ki********@hot mail.comREMOVET RAIL> wrote in message
news:OY******** ******@TK2MSFTN GP10.phx.gbl...

"Michael C#" <ho***@boutdat. com> wrote in message
news:eU******** ******@TK2MSFTN GP09.phx.gbl...

Hehe. Then use DateTime.MaxDat e and let the
great-great-great-great-great-great-great grandkids deal with the Y10K
problem.

Yeah...

Are you sure that January 1st, 9999 is far enough in the future though?

8-{p

Mythran

I'll be long dead and gone by then, and it'll be an S.E.P. (Somebody Else's
Problem)

Just wondering, but has anyone ever stored a Date in their database beyond
say -- just to throw an arbitrary date out there -- 5000 C.E.? I've seen
some databases with dates as high as 2399 C.E. (guy with like 4 life
sentences, no possibility of parole), but beyond that...? Just wondering if
maybe it's a common occurrence in some parts of the world to store such high
dates.

[Oenone]

Michael C# wrote:

Just wondering, but has anyone ever stored a Date in their database
beyond say -- just to throw an arbitrary date out there -- 5000 C.E.?

Nothing that's supposed to be there. Loads of users have mis-keyed the year
when entering dates and we've ended up with dates in 9199 and things like
that.

The most common date in any of our systems is the 30th December 1899. Spot
the app that was originally written in VB6. :-)

--

(O) e n o n e