Data Model

[goslincm]

I've been trying to self teach and learn from this forumn and articles out here. I'm not certain I'm getting the concepts correctly. I am putting together a database to track policy and numbered letter reviews and revisions. Can you tell me if this looks correct:

STAFF---(completes)---FORM----(assigned)----GROUP----(approves)----STAFF----(generates)--REVISION-----(gets)--PUBLISHED

 

[GingerR]

Hi. I don't understand your "diagram".
Please post your table(s) structures and tell us how each entity is related (i.e. a Policy can have one or more Reviews, etc)

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at

http://r937.com/relational.html

 

[SkipVought]

I think that he's using an Entity Relationship Diagram.

Skip,

_[red][/red]

 

[goslincm]

Yes Skip that is what I was trying to put in place first to determine if I was going in the right direction. I thought that was my first step, and then it is to create the attributes within each ENTITY. Am I wrong?

 

[GingerR]

Still doesn't do it for me. Good luck.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at

http://r937.com/relational.html

 

[fneily]

Even before you build an ERD, you still have to create your tables.
I would suggest you create your tables first. Each table is a topic. Only fields that relate to that topic should be in the table. Then go through Normalization. This will probably create more tables. After they're normalized, then set up your relationships. You may have some many-to-many which will need junction tables to resolve the relationship. For one-to-many, you will create foreign keys. Then go back and put in any input masks, formats, data validation, required/not required, etc. properties on each field in all the tables. Now you can create your input, edit, information forms, queries, reports. If your tables are set up correctly, data analysis falls right out.

 

[goslincm]

Thanks for taking the time to explain Fneily, I really appreciate it.