> murray... > > it may have been helpful to the guy to also give him an idea of your tbl > structure. i think you're talking about something like: > tbl schema > > EvalTBL > -id > -UserID > -ScoreTypeID > > ScoreTBL > -id > -ScoreType > > table ScoreType could/would have as many different categorites as > required. > table EvalType would have a scoreTypeID (from the ScoreTBL) for each > userID. > each user could have multiple scoreTypes in the EvalTBL... Hi bruce, That would have been an even more normalized representation of the table(s), yes. For the purposes of demonstrating a state of normalization that still allowed the OP to maintain a single table, my structure in that post was: Scores -ScoredThingID -scoretype -score I would personally have implemented a structure similar to the one you outlined, but posted with the idea of "first things first". That's why I included a link to a tutorial on normalization and suggested Googling on the topic as well, for further reading. Still and all, it's helpful of you to clarify. Much warmth, Murray --- "Lost in thought..." http://www.planetthoughtful.org -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
