First what are you trying to manage
Get the the thinking hat on and group what u want to store.
So table would be clients
Fname = first name
Ok what I do when building a database I get heaps of A4 paper one A4 for each table and write down what I think should be in be table A4 paper then when to start dup items that mean that item should be in it's Owen table ( new A4) and link that tableid is stored in that table.
Hope that help get the ball rolling.
hope this help
See clear as mud
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.