specifying a date literal?

[djc]

MyVariable = #1/1/2099#, which is how I used to do this, throws an
exception? "... "cannot be converted to type date". So I'm assuming there
was a syntax change in .net? To be more specific, the line of my code
causing the compile error is this:

val_rv_txtETA.MaximumValue = #01/01/2099#

val_rv_txtETA is an asp.net rangevalidator control.

any info would be greatly appreciated. Thanks.

[Cor Ligthert]

DJC,

In my opinion the most sure way in all cultures

dim whateverdatetimeformat as datetime = new datetime(2099,01,01)

I hope this helps,

Cor

"djc" <no***@nowhere.com>

MyVariable = #1/1/2099#, which is how I used to do this, throws an
exception? "... "cannot be converted to type date". So I'm assuming there
was a syntax change in .net? To be more specific, the line of my code
causing the compile error is this:

val_rv_txtETA.MaximumValue = #01/01/2099#

val_rv_txtETA is an asp.net rangevalidator control.

any info would be greatly appreciated. Thanks.

[Herfried K. Wagner [MVP]]

"djc" <no***@nowhere.com> schrieb_

MyVariable = #1/1/2099#, which is how I used to do this, throws an
exception? "... "cannot be converted to type date". So I'm assuming there
was a syntax change in .net? To be more specific, the line of my code
causing the compile error is this:

val_rv_txtETA.MaximumValue = #01/01/2099#

.... works fine for me (if 'MaximumValue' is of type 'DateTime' (= 'Date').

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

[djc]

thanks for the reply. I appreciate it. I don't know why but as long as I
first put the values for MinimumValue and MaximumValue in the asp.net
RangeValidator tag itself (like so: MinimumValue="1/1/2004"
MaximumValue="1/1/2099") then I can change those properties programatically
as the line from my original post does. If they are not there in the asp tag
then when I try to change them programatically I get that error...
strange... well, strange unless you know why. hehe.

thanks again.

"Cor Ligthert" <no************@planet.nl> wrote in message
news:u7**************@TK2MSFTNGP09.phx.gbl...

DJC,

In my opinion the most sure way in all cultures

dim whateverdatetimeformat as datetime = new datetime(2099,01,01)

I hope this helps,

Cor

"djc" <no***@nowhere.com>

MyVariable = #1/1/2099#, which is how I used to do this, throws an
exception? "... "cannot be converted to type date". So I'm assuming there was a syntax change in .net? To be more specific, the line of my code
causing the compile error is this:

val_rv_txtETA.MaximumValue = #01/01/2099#

val_rv_txtETA is an asp.net rangevalidator control.

any info would be greatly appreciated. Thanks.

[djc]

thanks for the reply. I appreciate it. I don't know why but as long as I
first put the values for MinimumValue and MaximumValue in the asp.net
RangeValidator tag itself (like so: MinimumValue="1/1/2004"
MaximumValue="1/1/2099") then I can change those properties programatically
as the line from my original post does. If they are not there in the asp tag
then when I try to change them programatically I get that error...
strange... well, strange unless you know why. hehe.

thanks again.

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:eX****************@TK2MSFTNGP14.phx.gbl...

"djc" <no***@nowhere.com> schrieb_

MyVariable = #1/1/2099#, which is how I used to do this, throws an
exception? "... "cannot be converted to type date". So I'm assuming there was a syntax change in .net? To be more specific, the line of my code
causing the compile error is this:

val_rv_txtETA.MaximumValue = #01/01/2099#

... works fine for me (if 'MaximumValue' is of type 'DateTime' (= 'Date').

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