M
MES via AccessMonster.com
I am having trouble figuring something out and hoping someone out there might
be able to help.
I have built an Access database for a hospital education department to track
education activities that employees have taken and/or need to take. I have
built into the structure a means of requiring a specific job code to take a
specific activity, or employees from a specific department to take an
activity. I have tables set up - Employee, JobCodes, Depts, JC_Requirements,
and Dept_Requirements. Each employee has a Dept_Num and a JC_Num. These
fields are linked to the Dept and JC tables. Each table is linked to a
separate requirements table (please be assured that this database is
normalized). So if an employee has a specific job code and/or a specific
department, they would be required to take an activity that is required for
either the job code or department. For example, if JC_Num is required to
take Course_Num, then JC_Required =1 (has to take), else equals zero (doesn't
have to take). Further if Dept_Num is required to take Course_Num, then
Dept_Required =1, else 0. So in my database, an employee can be required to
take and activity either because of their job code or because of the
department they are in.
My set-up seemed to work fine until we realized that there are certain
activities that a job code would be required to take, but only if that job
code was in a specific department. For example, only an RN in Maternity
department would be required to take the Neonatal Resuscitation activity, not
RN's in other departments in the hospital. Originally, there were so few of
these exceptions that I was able to add code (in the form of an if/then
statement) to a query. (If JC_Num = (RN) and Dept_Num = (Maternity), then
Required = True, Else Required = False). However, we have more and more
exceptions, and I have found that I only have so much space in the field in
the query for this code, so I am now at the limit. I tried assigning aliases
to shorten the amount of space I'm taking up in the field, but I again filled
it up.
I am looking for advice on what to do next. I think that I need to alter my
database structure somewhat to accomodate this, but I can't think of any way
to do this. Would anyone know how to handle this?
Thanks in advance for your help.
MES
be able to help.
I have built an Access database for a hospital education department to track
education activities that employees have taken and/or need to take. I have
built into the structure a means of requiring a specific job code to take a
specific activity, or employees from a specific department to take an
activity. I have tables set up - Employee, JobCodes, Depts, JC_Requirements,
and Dept_Requirements. Each employee has a Dept_Num and a JC_Num. These
fields are linked to the Dept and JC tables. Each table is linked to a
separate requirements table (please be assured that this database is
normalized). So if an employee has a specific job code and/or a specific
department, they would be required to take an activity that is required for
either the job code or department. For example, if JC_Num is required to
take Course_Num, then JC_Required =1 (has to take), else equals zero (doesn't
have to take). Further if Dept_Num is required to take Course_Num, then
Dept_Required =1, else 0. So in my database, an employee can be required to
take and activity either because of their job code or because of the
department they are in.
My set-up seemed to work fine until we realized that there are certain
activities that a job code would be required to take, but only if that job
code was in a specific department. For example, only an RN in Maternity
department would be required to take the Neonatal Resuscitation activity, not
RN's in other departments in the hospital. Originally, there were so few of
these exceptions that I was able to add code (in the form of an if/then
statement) to a query. (If JC_Num = (RN) and Dept_Num = (Maternity), then
Required = True, Else Required = False). However, we have more and more
exceptions, and I have found that I only have so much space in the field in
the query for this code, so I am now at the limit. I tried assigning aliases
to shorten the amount of space I'm taking up in the field, but I again filled
it up.
I am looking for advice on what to do next. I think that I need to alter my
database structure somewhat to accomodate this, but I can't think of any way
to do this. Would anyone know how to handle this?
Thanks in advance for your help.
MES