Here, our Civil Engineering Folks have what they call MAS sheets.  They are two pages.  The first page is work to be done on a particular piece of equpment.  Some have five things, some have three, some have 7, so-on and so-on.  The second page is what was done, the date it was done and the initials of the worker who did it.  My problem is I am trying to normalize the data base so I won't one big huge giantic monsterous out of this world table.  Ther are 9 fields that have the capability of haveing 10 different entries.  I want to break the HUGE table down to ten smaller ones.  When I do that, I want to be able to bring up a MAS Sheet for a particular piece of equipment and just have what is particular for that piece of equipment.  I am not sure quite how to do that.  I know it has something to do with the ID.

Any help will be greatly appreciated........................

            

____________________________
C.......................

helloo...

i always ask these from those who needs help on normalization from my friends..

1. list down all the things you want to record.
2. group similar attributes to form one entity
3. and etc...

anyway, i you may, can u please post all the things you want to record so we could take a look at it..

    

andrew

Just curious really.... but unless you're having poor performance and optimized queries for retrieving data, is there any other reason to make the table smaller?

Afterall, if you have a program or front-end to the database, not all the fields or rows are used at once.


To keep something in mind also, it is possible that by having multiple tables over a single table, it could take a bit longer to retrieve the data (ex: instead of one "SELECT" you have multiple "SELECT" statements or "INNER JOIN" or similar to retrieve the same data)

of course, you could just make 10 copies of the table structure, then import the data that belongs there.  Then every query will have to be modified to make sure it uses the proper table, and potentially not trying to access a field that doesn't exist.  It could end up in a major re-write of the program as well.

____________________________
Everywhere's Local (classifieds, job postings, & more for everycity in the world - user entered)

JL
I was think about that all day.  Since there are three major areas, I decided to have three seperate tables.  They will contain some similar information which is common to all.  However, there is enough different information to let them stand alone.  Each has varing degrees of who what and when.

Thanks......................you said just enough to convience me.

Who said thinking was just for mortals.....................


      

____________________________
C.......................