If you mean what I think you mean you need to have a "components" setup (that's just my name for it).
Create this table (bare minimum columns here): Components: - Columns: ComponentID, ParentComponentID, isActive, Title, Basically, you can have parents and child components (or tables, etc) all in one table with the linkage happening between ParentID and ParentComponentID. You could then query it quite easily. Example - Let's say ComponentID 1 is what you are seeking. To get all of the children simply: SELECT * FROM Components WHERE ParentID = 1; Obviously this could get quite big if you have children of children. This table works quite well in several situations. Hope this helps... On 2/20/06, Ken <[EMAIL PROTECTED]> wrote: > > Hi. Does anyone know how to do this in the most efficient manner? Take a > look at this: > http://base.google.com/base/processstep1offer > > I need to be able to add custom fields to the database. And then later be > able to search those fields running sql statement. > > Any bright ideas? > > Thanks, > K > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232957 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
