VBA DateValue formula now gives VB error for an empty string

[Nelson Johnson]

Hi everyone. Has anyone else noticed a change recently, in how DateValue behaves in VBA? I am fairly sure that a few months ago, I tested something like this below in a tool I was developing, and it always worked OK when the string variable stCellVal was empty:

ActiveCell.Value = DateValue(stCellVal)

Even running a query in the immediate window as below, now gives error 13, the same as the above does:

?DateValue("")

The same thing happens in both Excel 2010 and 2013.

Has this changed in Excel in the last few weeks or so - and it didn't used to result in a VB error at all - or is my memory dodgy, and it was always like this?



Many thanks,
Nelson

[Andy Pope]

I think it has always been like that. Sure you didn't have On Error Resume Next or to go to an error handler?