Re: Inspection Sheet
- From: "tina" <nospam@xxxxxxxxxxx>
- Date: Tue, 12 Jul 2005 03:35:43 GMT
"each ***" = one inspection, correct? if so, something along these lines
might be appropriate:
tblQuestions
QuestionID (primary key)
QuestionText
tblInspections
InspectionID (pk)
Builder
Subdivision
Lot
Superintendent
Crew Leader
Inspector
InspectionDate
tblInspectionAnswers
AnswerID (pk)
InspectionID (foreign key from tblInspections)
QuestionID (fk from tblQuestions)
Pass/Fail
Floor
Direction
note: assuming that the Floor and Wall data will only be entered for a
particular question when Pass/Fail = Fail, i might remove those two fields
to a separate table, as
tblInspectionAnswers
AnswerID (pk)
InspectionID (foreign key from tblInspections)
QuestionID (fk from tblQuestions)
Pass/Fail
tblAnswerDetails
AnswerID (primary key AND foreign key from tblInspectionAnswers)
Floor
Direction
hth
"Greg" <Greg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7B31801-298E-4522-99A8-1ADDAE736692@xxxxxxxxxxxxxxxx
> I am building a database to store information from housing inspections. I
> have 29 question each with a Pass/Fail check box, a floor indicator(What
> floor the defect is on), and a Direction (which wall). I am not sure the
best
> way to go about creating this.
> In addition to this Each *** has a Builder, Subdivision, Lot,
> Superintendent, Crew Leader, Inspector, and Inspection Date. I am having
> trouble setting up the heirarchal structure.
> I would appreciate any help. I am relatively new to Access and may need a
> little bit more focused response.
>
> --
> Greg
>
.
- References:
- Inspection ***
- From: Greg
- Inspection ***
- Prev by Date: Re: census database design
- Next by Date: Re: Inspection ***
- Previous by thread: Inspection ***
- Next by thread: Re: Inspection ***
- Index(es):