>>>>No problem and I don't care if you use or not. Woould you tell me what do you mean by "since this class returns an incorrect result"?
>>>>Cetin
>>>
>>>

>>>WITH CREATEOBJECT("age")
>>>
>>>	.CalcAge({^1988/2/29} ,  {^2006/09/21 })
>>>
>>>	CLEAR
>>>	
>>>	? .Years , .Months , .Days
>>>	* CHECK with the correct definition Age = (((Birth+Y)+M)+D)
>>>	?  GOMONTH(GOMONTH({^1988/2/29},.Years*12),.Months)+.Days
>>>	* CHECK with a bad definition
>>>	?  GOMONTH({^1988/2/29},.Years*12+.Months) + .Days
>>>	?  gomonth(GOMONTH({^2006/09/21} - .Days, - .Months), - .Years *12)
>>>ENDWITH

>>
>>18 years, 6 months and 22 days. Correct. I don't understand why you say it's a bad definition. Use pen and pencil.
>>Cetin
>
>Using this method you can not arrive to the same point. None of the dates match.

What point are you talking about? Simple math it is and in code ypu could do:

? GOMONTH(DATE()-22,-6-18*12)

Cetin