Missing Data

  • Thread starter Thread starter AGOKP4
  • Start date Start date
A

AGOKP4

hi all,

I need suggestions on how to capture/track missing data.

In my query with 3 age groups <40, 40-60 and >60, I currently have

Age Group: IIf([Age]<40,"40<",IIf([Age]>=40 And
[Age]<60,"40-60",IIf([Age]>60,"60>")))

What can I do to track missing data?

Thanks
 
Age Group: IIf([Age]<40,"40<",IIf([Age]>=40 And
[Age]<60,"40-60",IIf([Age]>60,"60>", "***Missing***")))

One other point. It appears you are storing an age in your table. Bad
idea. ages change over time and it is a value that can be calculated. The
correct method is to store the person's birthday and calculate the age based
on the birthday when you need to reference the person's age.
 
Klatuu,
You are making an assumption that the database is collecting the date of
birth. Some times all that is collected is the age of the person at the time
of the event being recorded. Date of Birth is an identifier that is sometimes
used in security systems and is also considered in health related databases
(in the US) as restricted information (personal health information).

I agree that in many (if not most) cases it is best to collect the date of
birth and calculate the age when needed.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
 
Thanks for additional information, John.
I was not aware that HIPPA considered DOB restricted info.
I have never personally seen a situation where DOB or age were an issue of
security. I have seen where age at entry was kept, but even then we
calculated off DOB which was stored and used for other things.
--
Dave Hargis, Microsoft Access MVP


John Spencer MVP said:
Klatuu,
You are making an assumption that the database is collecting the date of
birth. Some times all that is collected is the age of the person at the time
of the event being recorded. Date of Birth is an identifier that is sometimes
used in security systems and is also considered in health related databases
(in the US) as restricted information (personal health information).

I agree that in many (if not most) cases it is best to collect the date of
birth and calculate the age when needed.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
Age Group: IIf([Age]<40,"40<",IIf([Age]>=40 And
[Age]<60,"40-60",IIf([Age]>60,"60>", "***Missing***")))

One other point. It appears you are storing an age in your table. Bad
idea. ages change over time and it is a value that can be calculated. The
correct method is to store the person's birthday and calculate the age based
on the birthday when you need to reference the person's age.
Click to expand...
Click to expand...
 
Hello Klatuu and John,

The expression worked....The database I created is for a study that requires
age not DOB and we are just looking at a single time point not over time.

THANKS so much for your replies.

Klatuu said:
Thanks for additional information, John.
I was not aware that HIPPA considered DOB restricted info.
I have never personally seen a situation where DOB or age were an issue of
security. I have seen where age at entry was kept, but even then we
calculated off DOB which was stored and used for other things.
--
Dave Hargis, Microsoft Access MVP


John Spencer MVP said:
Klatuu,
You are making an assumption that the database is collecting the date of
birth. Some times all that is collected is the age of the person at the time
of the event being recorded. Date of Birth is an identifier that is sometimes
used in security systems and is also considered in health related databases
(in the US) as restricted information (personal health information).

I agree that in many (if not most) cases it is best to collect the date of
birth and calculate the age when needed.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
Age Group: IIf([Age]<40,"40<",IIf([Age]>=40 And
[Age]<60,"40-60",IIf([Age]>60,"60>", "***Missing***")))

One other point. It appears you are storing an age in your table. Bad
idea. ages change over time and it is a value that can be calculated. The
correct method is to store the person's birthday and calculate the age based
on the birthday when you need to reference the person's age.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top