Tables
Listing
AttributeListing
AttributeClass
Attribute
-l is a listing, so l.id is the primary key of the Listing Entity which I already have.
-Attribute is a table holding generic attributes which may apply to different classes.
-AttributeClass is a table storing the IDs of the Attributes which apply to a particular Class ID.
-AttributeListing is a table storing both the ID of the AttributeClass and the ID of the Listing (this combination is unique) which then has some extra fields to store information which the user may supply for this particular listing.
So, whenever I pull up a Listing, I either a) create a new one, or b) load up an existing one. It it already exists, I need to use this ListingID to pull up all Attributes through the AttributeClass table, linked from the AttributeListing table.
Anyway, just seemed like I was supplying a lot of code for doing something relatively simple. If this is just 'the way it is', then I can live with that - but I thought it would behoove me to reach out and ask. I am willing to go back to the designer and add stuff, or rewrite the code - just looking to maximize my investment in LLBL Gen Pro.
Thanks!
Josh