Art I take it each of the first group has a primary key. You could use one Notes table with a foreign key and a Notes field. Maybe even throw in a date field for when the note was written and a user ID for whomever wrote the note. Rows would look like this: 1, UnitID, This unit could stand some painting, 6/23/2012, bill_m --- In ms_access_professionals@yahoogroups.com, <dbalorenzini@yahoo.com> wrote: 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
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (7) |
Tidak ada komentar:
Posting Komentar