I guess the whole issue is because the inbuilt functions are not designed to alter the argument types that need to passed when they are in all 32 bit or all 64 bit combinations of Excel and Windows. He suggested that an easy workaround would be to convert the LongPtr variables to Long using the CLng function. Because of that, in such cases, the add-in will not work. He suggested that when the add-in is run in Excel 64 bit version run on Win 7 64 bit, some of the functions like MonthName returns an error because we are passing the month index argument as a LongPtr, rather than a Long variable.
Wasn't able to spend time on the forum over the last couple of weeks as I was busy with client visits at work, and had to focus attention there at work.Īnyway, a good man, Neil Holder, an Excel enthusiast like most of us, has given a valuable insight about the Ribbon Date-picker I developed. PS: Nothing related to this topic, but just talking about languages and localizations I remebered this, and maybe you want to give a look at it: (*) Just for being purist, it'd be wonderful if the words Day and Calendar should adopt the localized names. bottom right: drop down for day selection (Ok, local language, starting week changed to Monday - Lunes) bottom left: drop down for day selection (Ok, local language, default week starting on Sunday - Domingo) top right: drop down for month selection (Ok, local language) Please check in the uploaded image how does it work with another language version: Thank you very much for the modifications. Sorry for not having answered yet but sometimes I'm powered off as much as possible, not only from computers & internet but from the world if I can. Points a) & b), as you said c), last option, use the local language for Day d), exactly, "Mo|Tu|.|Su".
First of all, all your assumptions were correct.