Of course I don’t agree at all with Mack. He/she either never uses relational databases with inter-related tables or he/she writes all the logic necessary to ‘join’ table data in his/her code.

Thanks again.

Of course I don’t agree at all with Mack. He/she either never uses relational databases with inter-related tables or he/she writes all the logic necessary to ‘join’ table data in his/er code.

Thanks again.

This must be where the order number table you describe in the introduction comes in, but I can’t seem to wrap my head around the fact that each order, while having one customer id, would have multiple pens. Would you get around this by providing multiple generic fields (product1, product2, etc) or would you want to store multiple product id’s in one field by concatenating them ($a = product1; $b = product2; $c = product 3; $delim = ‘,’; $storstrng = $a.$delim.$b.$delim.$c; //returns a string “product1,product2,product3″) and using a php explode to return the results in a readable format?

I’m curious which would be optimal. I hope there is an easier, more appropriate solution.

I think you did a good job explaining them and your visuals were very helpful.