Tbl design Date Problem

[Linda RQ]

Hi Everyone,

I have to keep track of employees credential dates. We need to enter in the
expiration date but some employees do not have an expiration date because
they were "granfathered" so these employees do not have an expriation date.
How should I handle this?

My fields will be

tblCredentialType
CredentialTypeID (PK)
CredentialType

tblCredentials
CredentialsID (PK)
EmployeeID (FK)
CredentialTypeID (FK)
CredentialExpirationDate


Thanks,
Linda

 

[fredg]

Hi Everyone,

I have to keep track of employees credential dates. We need to enter in the
expiration date but some employees do not have an expiration date because
they were "granfathered" so these employees do not have an expriation date.
How should I handle this?

My fields will be

tblCredentialType
CredentialTypeID (PK)
CredentialType

tblCredentials
CredentialsID (PK)
EmployeeID (FK)
CredentialTypeID (FK)
CredentialExpirationDate

Thanks,
Linda

I don't know! How do you want to handle it?
Form me, the easiest way is to Update the table and set all
grandfathered Expiration dates to any improbable distant date, i.e.
12/31/2222.
But how will you know which employee is grandfathered in or not?

Something like ....

Update YourTable Set YourTable.CredentialExpirationDate =
#12/31/2222# Where YourTable.[?SomeField?] = ?;

Fill in the ? above.

As I have no idea what you are wanting to do with the data, other than
giving the data as a far distant date you might want to leave it null,
and test for Null whenever you need to do something with it:

If IsNull([CredentialExpirationDate]) Then
Do this
Else
Do that
End If

 

[LMB]

Hi Everyone,

I have to keep track of employees credential dates. We need to enter in
the
expiration date but some employees do not have an expiration date because
they were "granfathered" so these employees do not have an expriation
date.
How should I handle this?

My fields will be

tblCredentialType
CredentialTypeID (PK)
CredentialType

tblCredentials
CredentialsID (PK)
EmployeeID (FK)
CredentialTypeID (FK)
CredentialExpirationDate

Thanks,
Linda

I don't know! How do you want to handle it?
Form me, the easiest way is to Update the table and set all
grandfathered Expiration dates to any improbable distant date, i.e.
12/31/2222.
But how will you know which employee is grandfathered in or not?

Something like ....

Update YourTable Set YourTable.CredentialExpirationDate =
#12/31/2222# Where YourTable.[?SomeField?] = ?;

Fill in the ? above.

As I have no idea what you are wanting to do with the data, other than
giving the data as a far distant date you might want to leave it null,
and test for Null whenever you need to do something with it:

If IsNull([CredentialExpirationDate]) Then
Do this
Else
Do that
End If

Thanks for responding, Fred. I have been looking at some other posts and
perhaps I need to go to the getting started group or table design because I
am not ready to work with "code" yet. I'm not really sure what Update your
table set means or where that would be typed. I also think I need to.....
as you say differentiate between grandfathered and not grandfathered because
if I didn't put a date in, I could mistake a person who's date just got
deleted or not entered for someone who doesn't need to renew their
credential. The purpose of this is to make sure the employees have their
credentials. The employees who have been grandfathered do not need to renew
their credentials. Once an RRT, always an RRT for those people. Employees
who became an RRT after a certain date have to renew their status every 5
years, if they do not, they are no longer an RRT and will have a drop in
pay.

Linda