I can't be sure from your description, but it sounds like you are using
columns to hold different "gradings of a phone call". If so, this sounds
more like a spreadsheet than a relational database.
If you are saying that, for any given phone call, zero, one or more elements
of the call could be graded, by zero, one or more supervisor-types, then
your table might need to look more like:
trelCallGrade
CallGradeID (a primary key)
CallID (a foreign key, pointing to a tblCall ID -- which call)
GradingElementID (foreign key, pointing to tlkpGradingElement, a
list of possible elements)
SupervisorID (foreign key, pointing to tblEmployee table - who
graded this element on this call)
Grade
GradeDateTime (a date/time field noting when the grading was done)
Regards
Jeff Boyce
Microsoft Office/Access MVP
"Bunky" <(E-Mail Removed)> wrote in message
news:4D9084BA-ECB9-4F2A-8A83-(E-Mail Removed)...
>I have a table that contains about 35 different data elements concerning
>the
> grading of a phone call. Normally, the supervisor listens to the call and
> grades it based on the data elements being evaluated. However, the
> Quality
> Manager was wondering what element was being missed the most. Each
> associate
> can have 3-6 monitoring scores per week. The scoring can be either all or
> none of the points associated with that element. Example: Appropriate
> Greeting is worth 2 points; the associate must get either 2 points or
> none.
>
> With all this being said, how should I approach this? In other languages,
> ie COBOL, I know exactly what I would do, but with access I am rather
> hesitant. Any ideas, would be appreciated.
>
>
|
Similar Threads
