>>
>>You can have a Key in your Property table to another table, called, say, ExtraInfo. The ExtraInfo table will have this key that may define one or more records with TABLE_NAME FIELDS_NAME, JOIN_TYPE, etc. fields.
>>
>>So, if your key in Property table is null, you only select from main table. Otherwise you now may have joins to other tables. All this assumes simple select statements (no derived tables, no grouping, etc.)
>>
>>Also where and how do you define WHERE condition?
>
>I like your idea of having one Key in the property table with Extra Information, rather than having it all in several properties. I will play with this idea.
>
>The WHERE is pretty simple, it is either ALL or nothing. And this is set as an application preference.
>
>Thank you for your suggestion.
You're welcome.
If it's not broken, fix it until it is.
My Blog