Is this bad design?

Table A Id (PK) Field1 (FK to TableB.Field2)

Table B Id (PK) Field2

I noticed that LLBL will not detect relationships where both sides are non-PK, but in some cases you can avoid a junction table by using a GUID data type in this manner.

Ben

Is there a relationship defined between the fields in the database? Is TableB.Field2 unique?

Chester wrote:

Is there a relationship defined between the fields in the database? Is TableB.Field2 unique?

Yes. See http://llblgen.com/tinyforum/Messages.aspx?ThreadID=6863&HighLight=1 for info about the non-PK problem.

OK, I missed that fact that you were asking an Architecture question. Sorry.

I'm not sure how the design avoids a junction table if the cardinality of the relationship is many-to-many. I've seen the use of bitmaps to do this, but I can't see how guids would be used in this scenario. The bitmap field is stored as an integer, where each bit represents a fact or entity. It can increase performance for intersections with relatively small domains.