Hi:

I´m about to start a project for the company for which I own a franchise, is a fast food mexican restaurant. They sent me their inspection form and to sum it up is something like this.

Quality

Meat had required temperature: 15 points

Meat looked the right color and looked correctly cooked: 10 points

Turkey had required temp... : 15 points

and goes on with all ingredients and items.

Then we have another section out of many others like:

Appeareance

Restaurant is to standards: 10 points

etc.......

Customer service

Client 1

Hospitality 10 points

Preparation time 10 points

and many other items, etc.

and so on then client 2, client 3, etc.

What I thought was to have like a database that the requirements would be flexible and have like a Section Table for Appearance, Quality, etc. Then an Item Being Inspected Table that would be linked to the section table. So basically treat Items being inspected like a products table.

Then I would have an Inspection table with a lines table. Then generate the lines with scripts, the problem is with customer service section that would be like a sub of lines table. That´s where I´m stuck. So what do you think? Is this the right approach or should I just have a table that holds all questions as fields? In my analysis that didn't make sense since I would have over 300 fields for a single table.

Anyways guys any idea would be greatly appreciate it.

Andre

should I just have a table that holds all questions as fields?

No, you should have a table that holds all questions as records. Then you should have another table for the answers, and one for the inspections:

Inspections --< Answers >-- Questions

Dividing the questions into sections may be convenient, but it's not critical for the solution.

See also;

http://fmforums.com/...378#entry229378

http://fmforums.com/...urvey-question/

Thanks