topic Re: Age Function in QlikView

Age Function

Anonymous — Wed, 25 Nov 2020 16:16:04 GMT

Hey There,

i use on my data model at the age function & Interval for some reason i get not the right age, any idea what im doing wrong ?

On sql servel i use this "DATEDIFF(Year,E.BirthDate,GetDate()) EmployeeAge" but i know datediff does not work on qv so i try this other method.

Regards

David

Re: Age Function

swuehl — Mon, 18 Apr 2016 09:50:50 GMT

Isn't the right age 39?

Re: Age Function

Anonymous — Mon, 18 Apr 2016 09:52:06 GMT

Look at the Interval

Re: Age Function

sunny_talwar — Mon, 18 Apr 2016 09:52:32 GMT

I agree the age will be 40 on May 15th, isn't it?

Re: Age Function

swuehl — Mon, 18 Apr 2016 09:54:29 GMT

The interval is showing a rounded number, right? So basically a rough estimation how many years have passed between dates. But that's not "age" as I would define it (which is more like a floor'ed number).

Re: Age Function

sunny_talwar — Mon, 18 Apr 2016 09:55:00 GMT

I got 39, when I put this in a text box object

=Interval((Today() - MakeDate(1976, 5, 15))/365, 'D')

Re: Age Function

swuehl — Mon, 18 Apr 2016 09:56:59 GMT

Maybe you can explain what you want to calculate? The age of a person? Then use the age() function.

Re: Age Function

Anonymous — Mon, 18 Apr 2016 09:59:15 GMT

I try To understand the diff between Interval Vs Age()

Re: Age Function

swuehl — Mon, 18 Apr 2016 10:00:33 GMT

Interval() is a formatting function, like Date() or Timestamp().

Age() calculates age.

Re: Age Function

lawrenceiow — Fri, 22 Jul 2016 12:00:28 GMT

Do you happen to know the accuracy of the Age() function?

Apologies for asking this in this post, please let me know if I should start a new post.

I always used to calculate age by dividing the days number by 365.25 as 365 was not accurate enough. Then, someone pointed out to me that Pope Gregory XIII had pointed out that Julius Caesar was incorrect in suggesting a year was 365.25 days long, it should be 365.2425. Hence the change from the Julian Calendar to the Gregorian Calendar.

So, do you happen to know how accurate Qlikview's Age() function is, the help screen does not specify?

Re: Age Function

swuehl — Fri, 22 Jul 2016 12:09:59 GMT

Are you talking about applying Age() to dates before year 1582, i.e. start of the gregorian calendar?

I believe QV will keep to the gregorian calendar and apply it's rules to the time before it was introduced (proleptic calendar). But I haven't tested it (haven't worked with databases containing these dates so far).

If your question is a concern about leap year handling, what concerns do you have exactely?

Re: Age Function

lawrenceiow — Fri, 22 Jul 2016 15:35:36 GMT

swuehl‌, my issue is simply to do with calculating a persons age. From my understanding (which may not be that great) dividing the days by 365.25 would be good enough for the living as it gains 1 day in 128 years. So in calculating the age which include the deceased I've since used 365.2425

Instead of using formulae such as

floor((eventDate-DateOfBirth)/365.2425) as PersonAge

I thought it might be neater to use

age(eventDate, DateOfBirth) as PersonAge

So, I just wanted to check that it would be safe to use this function.

Thanks for your help.

Re: Age Function

swuehl — Fri, 22 Jul 2016 22:43:59 GMT

I think the Age() function is more accurate in returning an integer number that is commonly regarded as age, i.e. increased by 1 each year whenever the day and month of the DateOfBirth value is reached.