Form Design Problems

[Guest]

Hi all,

I'm having a problem getting my head round one of my forms.

The business model is a call accreditation session (Where the team leader
sits down with recordings of customer services calls, and gives people points
based on certain criteria)

I have these tables related to this process:

Calls (Time, Date, Customer, Member of Staff making the call)
Sessions (Call ID, Staff ID, Criteria ID, Response)

So what I am doing is storing data about the calls in a different table, and
using the ID number of that call in the Sessions table to uniquely identify
the call.

What I can't figure out is how will I get people to enter this data via a
form? There is about 32 questions and they are all stored in another
database! It's a question per record, so the call ID, Staff name etc are all
reentered for the next record until all 32 questions have been completed...
Is there an easier way of doing this or am I going to have to copy the data
to each record until the session is finished?

Cheers

Toby

 

[Guest]

Try a form-subform approach. The data that needs to carry from one call to
another should be in the form, and the questions and associated info in the
sub form.

 

[Ian Davies]

Also in table 'Calls' the field 'Staff Making Calls' should be 'Staff ID'
and then have a separate table for Staff linked to it, like you have in
'Sessions' it will keep your database more streamline and faster in the long
run.

 

[Guest]

It's getting rather complicated now! I'm not sure what I need to do now! I
will try and upload a screenshot of my relationships!

I need to display all 32 questions so that the data can be entered but I am
not sure how to do this?

Toby

 

[Guest]

How would I display all 32 questions on the form at once if I didn't want to
use a listbox?

I was thinking of having 3 listboxes, 1 for the questions, one for passed,
and another one for failed, and then using the values in these boxes to run
an UPDATE query once it's completed!

I don't think there's any way I am going to be getting out of using SQL is
there?

Regards,

Toby