Thanks Fabian and Daniel In this case I think that Fabian is correct. The reason is that AssociationTableA also has about 10 other (many) relationships, so I chose to keep AssociationTableA as a normal entity with all of its relationships being 1:m, and make AssociationTableA m:m TableB.
Sorry, this all sounds very convoluted...but that's the database design! Thanks for your input and thoughts, Gareth. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
