Application.EOMONTH giving wrong answer

[baitmaster]

Edit: Application or Worksheetfunction, both giving same issue

Getting strange results in VBA when trying to work with EOMONTH. Debugging in Immediate I've got:

?format(WorksheetFunction.EoMonth(clng(Date),0),"dd mmm yyyy")

I'm expecting it to return 28 Feb 2018 but it's coming up with the 27th instead. Any ideas why?
I'm using CLNG because I'm in the UK and without it I'm getting an answer in 2010, trying to rule out US/UK date issues

Is there a known instability with VBA EOMONTH? Or is the answer staring me in the face but I just can't see it?!

Using Office Pro Plus 2013

Thanks

 

[Jonmo1]

You have the 1904 Date system checked in File - Options - Advanced.

 

[shg]

Wow, Jonmo -- good shot!

It's peculiar that that causef EF.EOM to fail but not EOMONTH in Excel.

 

[Jonmo1]

Yep, And I still don't understand why the EOMONTH (in vba with WorksheetFunction) would be the 27th

 

[baitmaster]

Thanks Jonmo, that was indeed the correct answer! The file was built off a dataset sent to me from an iPad which explains how this snuck in. Note to self: continue to dislike Apple products

 

[Jonmo1]

You're welcome.