It would probably be more beneficial to change the default format to something else.
AfaIk this is not possible. Or MS doesn’t allow it. User Defined would be pretty useless if MS would simply stop interpretating what I want to do in general
functionvalidate(val)
try:
cast val as numeric
except:
print"Oops, not a number"
cast val as general ## dateor whatever
end
validate(12.5) ## returns 12.5
validate("12.5") ## returns 12.5
validate("12 . 5") ## returns a date maybe
Thats a locale issues that excel has and cant fix ( for compatibility reasons ). Its one of the reasons i hate excel haha.
But not related to cell types
AfaIk this is not possible. Or MS doesn’t allow it. User Defined would be pretty useless if MS would simply stop interpretating what I want to do in general
function validate(val) try: cast val as numeric except: print "Oops, not a number" cast val as general ## date or whatever end validate(12.5) ## returns 12.5 validate("12.5") ## returns 12.5 validate("12 . 5") ## returns a date maybeOh my god what cursed Python, Lua, and SQL offshoot is this
It’s my own grammar, “Luanatic”
I mean, MS should change the default.
As a user, the only way currently is to make a template document and use that as a default when creating a new book.
You most certainly can. You can set the format of a cell, and if its set to number 12.5 will be 12.5, it wont even try date formats…
they’re talking about defaults, as in when you create a new file the first thing you do is type a number and not get interpreted as a date.
Try opening a sheet sent by a Spaniard colleague. Good luck with decimals.
Thats a locale issues that excel has and cant fix ( for compatibility reasons ). Its one of the reasons i hate excel haha. But not related to cell types
No, I know. I can fix it, but old sheets and stubborn colleagues and clients and my fucking grandma won’t.
My point was more related with excel manipulating input incorrectly because of Unspecified.