I'm currently developing a real estate system to manage order processing and work flow. I'm a little uncertain as to how to design the tables because an order can have N number of applicants, owners, buyers, and properties. There are cases where there are 9 different buyers and some where the number of properties exceeds 20. It seems that normalization might make the situation crazy, but I'm a touch rusty. Thanks.
I've actually been mapping out that kind of structure right now. It looks like there are many N:M relationships between the order id and its sub parts. A sweep around the different 'relationship' tables should give me my order.