I agree Duane, but the Attachment data type is useful in 2007 and later because
it provides a more efficient way to store documents and images. Unfortunately,
Attachment is also multi-value, so if you legitimately need to copy data using
INSERT, you'll have to write code instead of using an INSERT query.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Duane Hookom
Sent: Saturday, May 21, 2011 6:39 AM
To: ms_access_professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Re: Inspection Structure
IMO, multiple fields for multiple conditions is a bad idea. I would keep the
tables normalized. Every inspection value should create it's own record.
Duane Hookom
MS Access MVP
To: MS_Access_Professionals@yahoogroups.com
From: saccity101@yahoo.com
Date: Fri, 20 May 2011 14:18:31 -0700
Subject: Re: [MS_AccessPros] Re: Inspection Structure
tblRoom => RoomID, UnitID, RmTypID, ConditionID etc....
Not a problem !
Each room would have a record and you can track all the items needed on that
record.
Track as much as you want, floor material, I would recommend that you put date
fields in as well. So that when new carpet or window coverings are installed
you track the instal date.
tblCondition => CondID, New, Like New, Good, Serviceable, Needs Replacement
tblFloorMtl => FloorMtlID, Carpet, Leno, Paint, Cement, etc
tblRoom => RoomID, UnitID, RmTypID, CelingCondID,WallCondID, FloorMtlID,
FloorCondID, Notes, etc....
Opps! Sorry wrong this will not work.
Because you do not maintain a history with this method! Property Management it
is all about history and data management.
Will need to add a table for inspections, which would have the data about a
room.
tblInsp => InspID, RoomID, CelingCondID,WallCondID, FloorMtlID, FloorCondID,
Notes, etc...
tblRoom => RoomID, UnitID,
The point is that you want to be able to track when carpet was installed or when
the unit was painted.
You are standing in court doing an eviction and the tenant says that the carpet
was worn when they moved in. Nice to be able to say with confidence that it was
installed six months prior to when they moved in and it's condition was "Like
New"
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: Fri, May 20, 2011 2:00:25 PM
>Subject: Re: [MS_AccessPros] Re: Inspection Structure
>
>
>how do I cover multiple condition items (Ceiling condition type could be paint
>chipped, holes, etc)...
>
>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: Friday, May 20, 2011 3:13 PM
>Subject: Re: [MS_AccessPros] Re: Inspection Structure
>
>
>
>I would think that a many to many table between units and rooms would be ideal
>for this.
>A table of all units tblUnit => UnitID
>A table all room types tlbRoomTyp => RmTypID
>
>and a junction table to tie them together
>
>tblRoom => RoomID, UnitID, RmTypID, ConditionID etc....
>
>I assume that you have tables for Property and Building though building may be
>optional.
>Take care,
>Michael Simpson (916) 837-2211
>Sac City Plumbing
>3031 E St.
>Sacramento, CA 95816
>
>>
>>From: Bill Mosca <wrmosca@comcast.net>
>>To: MS_Access_Professionals@yahoogroups.com
>>Sent: Fri, May 20, 2011 12:52:08 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]
------------------------------------
Yahoo! Groups Links
Tidak ada komentar:
Posting Komentar