Should this VBA statement be ok: If Selection.Value = Evaluate("na()") Then

[TomCon]

I have a macro that runs daily. The above statement has been fine for a long time (year or more). Now it gives an error. (Error 2042). I am wondering if it is the result of a recent Office update.

The error is not coming from "Selection.Value" as that cell does not contain an error, it contains a valid value. In the immediate window:
?Selection.Value
works just fine to give the correct value

In the immediate window the following gives Error 2042:
?Evaluate("na()")
But, as i say, this statement has been working for a long time in that macro.

Any thoughts on whether "Evaluate("na()")" should work, or if there has been a recent change in behavior?

Thank you.

 

[RoryA]

That should always return an error value (2042).

 

[RoryA]

A reminder:

Cross-posting (posting the same question in more than one forum) is not against our rules, but the method of doing so is covered by #13 of the Forum Rules.

Be sure to follow & read the link at the end of the rule too!

Cross posted at:

Redirecting

answers.microsoft.com

There is no need to repeat the link(s) provided above but if you have posted the question at other places, please provide links to those as well.

If you do cross-post in the future and also provide links, then there shouldn’t be a problem.

 

[TomCon]

A reminder:

Cross-posting (posting the same question in more than one forum) is not against our rules, but the method of doing so is covered by #13 of the Forum Rules.

Be sure to follow & read the link at the end of the rule too!

Cross posted at:

Redirecting

answers.microsoft.com

There is no need to repeat the link(s) provided above but if you have posted the question at other places, please provide links to those as well.

If you do cross-post in the future and also provide links, then there shouldn’t be a problem.

Thank you for your link to the cross-posting rules. I'll keep it in mind. In this case i did not actually view them as the same question. The other was supposed to be about the policy of Office updates, while this was about VBA behavior. However, due to the response at the cross-post, the discussions did end up overlapping.