CompuServe Messages

Has anybody reported the DateValue bug in Visual Basic. Nothing in the knowledge base. Summary: DateValue takes a date in string form and produces the equivalent date/time serial number. If you leave out the year, DateValue is supposed to assume the current year. This works OK if the month is given as a number, but if the month is given as a name or abbreviation it makes an amusing conversion error. There is 1 Reply.