Validating a Date using IsDate doesn't seem to do the trick... 1

[KingRichard3]

The following evaluates as TRUE:

Isdate("1/1/'04") and Isdate("1/1/.04") and Isdate("1/1/04*")

Is it possible to use the IsDate() function to validate a date before sending it to a database? It seems to screen out all other bad input, but if the user inputs one of the above examples, the database is most unhappy...

Thanks,
Rick

 

[ca8msm]

The problem is that it sees it as a valid date. I would suggest writing it to a date variable first and then formatting it once it is in that variable (you can trap errors when assigning it to the date variable to account for any invalid dates). e.g.

        Try
            Dim MyDate As Date
            MyDate = "1/1/.04"
            ' Now apply the necessary formatting
        Catch ex As Exception
            ' Invalid Date
        End Try

----------------------------------------------------------------------

Need help finding an answer?

Try the search facilty (

http://www.tek-tips.com/search.cfm)

or read FAQ222-2244 on how to get better results.

 

[KingRichard3]

Great idea! It worked! (Until I input 3/305 - .NET's Date decided it was = 3/0305 and SQL Server decided to blow up when it saw that date...)


Rick

 

[ca8msm]

Yeah you may also have to implement additional checks such as a date range to make sure the year is between what you define as a valid range.

----------------------------------------------------------------------

Need help finding an answer?

Try the search facilty (

http://www.tek-tips.com/search.cfm)

or read FAQ222-2244 on how to get better results.