Hello
When you punch in a native function likeyou get a human-readable output, like 2/23/15. Yet a barebones UDF will spit out the excel representation of a date like 42058.
Please Login or Register to view this content.
Here's a brief UDF for the sake of example. What am I missing of get a human-readable date as output that will still behave like an Excel date?
Please Login or Register to view this content.
I would suggest a tutorial such as this http://www.cpearson.com/excel/datetime.htm to understand how Excel and VBA represent dates as a serial number. Recognize that the "human readable" output is merely an appropriate number format code applied to a cell containing an appropriate serial number.
Originally Posted by shg
I suppose the heart of my question is why can a native formula like =TODAY() seem to know to change the number format code from "general" to "date" automatically, but my UDF requires me to change the number format code from "general" to "date" manually. My concern is for the general user of my UDF who will likely not realize that the serial number represents a date.
There are few things that native Excel functions can do that VBA UDFs cannot do, and I think this is one of them. Yes, with native functions, Excel will somehow "recognize" that a function's output should be date and will automatically format the cell for you. I don't think you can get VBA UDFs to do the same thing.
Not the answer I was hoping to hear, but thank you for the information. I'm marking this one SOLVED.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks