In our application, we would like to have a generic entity (called FlexProperties) that can be used by (and contained within) a variety of other business objects.
In our normal approach, we would include ClassType and ClassID columns in the FlexProperty table, and then write code to associate the right FlexProperty object with the business entity object that contains it.
My question is how would we handle this with LLBL? We can't create a normal FK because the ClassID value could point to the PK in any of a number of other tables in the db.
Is a design like this compatible with LLBL, and if so, how should we approach it? Thanks!
