I understand where you are going with that but the user whats to be able to query by type (eg. How many units have holes in the walls in the entryway...)
With warm regards,
Arthur Lorenzini| SQL Server/Access Developer l alorenzin@live.com
Office: 605-338-0947| Mobile: 605-857-9137 | Fax: 605-338-0947
1316 E. 7th Street
Sioux Falls, SD 57103
SQL Server Development
Database Adminstration Services
Microsoft Access Development
Grant Writing TA Services
IT Assessment Services
Software Application Training
From: michael simpson <saccity101@yahoo.com>
To: MS_Access_Professionals@yahoogroups.com
Sent: Monday, May 23, 2011 11:08 AM
Subject: Re: [MS_AccessPros] Re: Inspection Structure
Art I always include a notes field with these conditional type fields.
Condition => New, Like New, Good, Serviceable, Poor, Needs Replacement.
Notes => used to describe the issues,
So a record would have Condition: Serviceable, Notes: Multiple chips and nail
holes in walls, aprox 30
Take care,
Michael Simpson (916) 837-2211
Sac City Plumbing
3031 E St.
Sacramento, CA 95816
>
>From: Art Lorenzini <dbalorenzini@yahoo.com>
>To: "MS_Access_Professionals@yahoogroups.com"
><MS_Access_Professionals@yahoogroups.com>
>Sent: Mon, May 23, 2011 8:58:33 AM
>Subject: Re: [MS_AccessPros] Re: Inspection Structure
>
>
>I uploaded the structure to the needs assistance folder. Maybe someone can take
>a look at what I got so far cause I am getting myself confused.
>
>With warm regards,
>
>Arthur Lorenzini| SQL Server/Access Developer l alorenzin@live.com
>Office: 605-338-0947| Mobile: 605-857-9137 | Fax: 605-338-0947
>
>1316 E. 7th Street
>Sioux Falls, SD 57103
>SQL Server Development
>Database Adminstration Services
>Microsoft Access Development
>Grant Writing TA Services
>IT Assessment Services
>Software Application Training
>
>From: Bill Mosca <wrmosca@comcast.net>
>To: MS_Access_Professionals@yahoogroups.com
>Sent: Friday, May 20, 2011 4:50 PM
>Subject: [MS_AccessPros] Re: Inspection Structure
>
>
>Then you need to add another row for that inspection of that unit in that room
>for that part of the room.
>
>It's kinda like taking inventory of a room with shelves that contain multiple
>products.
>
>Bill
>
>--- In MS_Access_Professionals@yahoogroups.com, Art Lorenzini <dbalorenzini@...>
>wrote:
>>
>> Not quite because the rooms inspection point condition can have multiple values
>>(eg. Wall Condition type: Water spots, paint chipped, holes )
>>
>>
>>
>>
>> With warm regards,
>>
>> Arthur Lorenzini| SQL Server/Access Developer l alorenzin@...
>> Office: 605-338-0947| Mobile: 605-857-9137 | Fax: 605-338-0947
>> Â
>> 1316 E. 7th Street
>> Sioux Falls, SDÂ 57103 Â
>> SQL Server Development
>> Database Adminstration Services
>> Microsoft Access Development Â
>> Grant Writing TA Services
>> IT Assessment Services
>> Software Application Training
>>
>>
>>
>>
>>
>>
>>
>> From: Bill Mosca <wrmosca@...>
>> To: MS_Access_Professionals@yahoogroups.com
>> Sent: Friday, May 20, 2011 2:52 PM
>> Subject: [MS_AccessPros] Re: Inspection Structure
>>
>> Â
>>
>> Art
>>
>> You shouldn't need a separate table for each room. You would have one table
>>with a UnitInspectionID (to get the unit info/date/etc.), RoomID, inspection
>>point (i.e. Floor, ceiling, wall, etc.), condition.
>>
>> So you have an inspection of Unit #123. You go into the Entryway and mark the
>>floor's condition as poor.
>>
>> Wouldn't that cover it?
>>
>> Regards,
>> Bill Mosca, Founder - MS_Access_Professionals
>> http://www.thatlldoit.com
>> Microsoft Office Access MVP
>> https://mvp.support.microsoft.com/profile/Bill.Mosca
>>
>> --- In MS_Access_Professionals@yahoogroups.com, "Art" <dbalorenzini@> wrote:
>> >
>> > I am struggling setting up a table structure for a house inspection database.
>>
>> >
>> > I have it setup like this but it does not seems to be right
>> >
>> > tblUnitInspection
>> > UNitInspectionID PK
>> > UnitID
>> > InspectionDate
>> > TenantTypeID
>> > TentPresentFlag
>> >
>> > Now in the inspection form has each room in the house broken out
>> >
>> > Entryway, Kitchen, Dining room, Living room,Hallway, Bathroom #1, Bathroom
>>#2, Attic, Bedroom #1, Bedroom #2, Bedroom #3, Bedroom #4, Utility
>>room,Stairwell, Basement, Exterior.
>> >
>> > I am looking at putting each room in it seperate table (eg.
tblUnitEntryway)
>> >
>> > tblUnitEntryway
>> > UnitEntrywayID PK
>> > UnitInspectionID
>> > FloorsCleanConditionTypeID - Lookup table tlkpCleanCondtionType
>> > FloorsTypeID - Lookup table tlkpFloorType
>> > FloorConditionTypeID - This is my issue, this is a key to the
>>tlkpConditionType table but I found out that they can select mulitple items. So
>>I know multi- value fields are bad so I am not sure what to do.
>> > FloorRepairsDesc - text
>> > WallCleanConditionTypeId - Lookup table tlkpCleanCondtionType
>> > WallConditionTypeID - same issue as above.
>> > WallRepairsDesc - Text
>> > CeilingCleanConditionTypeId - Lookup table tlkpCleanCondtionType
>> > CeilingConditionTypeID - same issue as above.
>> > CeilingRepairsDesc - Text
>> >
>> > And so forth and so on. I was think I could put the Floor, Wall, Ceiling into
>>seperate tables that will make for a whole bunch of table I don't think I need.
>>Any ideas?
>> >
>> > Thank you,
>> >
>> > Art Lorenzini
>> > Sioux Falls, SD
>> >
>>
>>
>>
>>
>> [Non-text portions of this message have been removed]
>>
>
>[Non-text portions of this message have been removed]
>
>
>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
Tidak ada komentar:
Posting Komentar