Yes, but that will be last date of preceding month.

add a month to get last date of the month the testdate is in

so :

AddDays(AddMonths(NewDate(Year(AGivenDate),Month(AGivenDate),1),1),-1)

Thank you it works

brilliant solution

Hi Akshay,

coding your own logic to determine last day of month is an inferior solution to using built-in functions, I think.

But more importantly, when you code your own logic to determine what is a leap year, make sure it is correct, this won't work for years that are a multiple of 100 but not 400.

Dorine

yes.as you say I had take care of the things of leap year, in that aspect I implement my approach

well yes, i see you have, but it's wrong

Ok. I think my approach is wrong but its working fine for me and I will go with that approach only . 

But anyway thanks for feedback.

try a date in februari of 1900 or 2100

Thanks for oml it helps me a lot to clear my concepts

Dorine Thanks for your feedback i have modify the things i am just lookinf for 100 years but thanks 

@pooja as i Check my OML helps you please download the new one to see the changes of leap years as well 

Hi Joao,

this is an interesting subject !

I don't yet have a clear idea of what I prefer, how i decide the following question :

When is a function / calculation too simple to bother adding an extra depency to a forge component and when is a function / calculation too complex to 'reinvent the wheel' as you put it.

For me, above formula is so simple that using a forge component feels like too much.

What is your take on this, is it a matter of consistency / best practice to always use from the forge when available, even if you can quickly code it yourself.  Are there any use cases where you would decide to code instead of use from the forge?  

Maybe you have a set of usefull forge components that you don't mind adding as dependency to all your projects because they are super stable and usefull.  If so, can you share some of those besides Date Time Utils you mentioned?

Dorine

Hi Dorine,

That's a very fair question.

From my experience, factories tend to grow and multiple applications built and in that regard, functions like the end of the month will probably not be the last utility datetime-related function one will use. Therefore I would prefer to refer to these kind of libraries / toolbox components that will help me down the road.

I would code it when I need to or don't find a forge component that can do it and that I trust the way it's done.

I actually created the Date Time Utils component from needs that an existing component (Extended Date Time, I think) didn't cope, which was client-side functions.

To avoid creating monoliths, I would not create a single module with all the utils, I would prefer to have different applications for different concepts so I would choose / look up a component for the scope I need (for instance, Math Utils, SEO Utils, etc.).