I have a cascading structure Owners, Properties, Buildings, Units and projects,
Each of these propagate down to the project table so that I can assign to any level
This may work for you as well, as each unit is within a structure, though a structure may have more than one unit. Thus on the note table for my data structure I can put a "ProjectID" Monthly reports shows all notes related to an owner.
Works for me.
Take care,Michael
>________________________________
> From: Art <dbalorenzini@yahoo.com>
>To: MS_Access_Professionals@yahoogroups.com
>Sent: Wednesday, August 7, 2013 8:24 AM
>Subject: [MS_AccessPros] Better structure maybe?
>
>
>
>I have a database with the following tables:
>
>Unit
>Exterior
>Structure
>Utilities
>...
>
>Along with these table I have the following tables that include notes and images about each of the primary tables:
>UnitNotes
>ExteriorNotes
>StructureNotes
>UtilitiesNote
>...
>
>As I was going through this I am thinking there has to be a better design than separate note tables for each of the primary tables. Any thoughts?
>
>Thank you
>
>Art Lorenzini
>Sioux Falls, SD
>
>
>
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (6) |
Tidak ada komentar:
Posting Komentar