See my breakdown. It puts many of the options into perspective. You will end up with a huge number of fields, but you might want to design this as somewhat of a OO design, with base object which you define, and ObjectExtension tables, which users can create, but then others can reuse.
Then you'd join the tlbObjects with tblExtImages or tblExtMediaFiles etc... Which would be strongly typed and well designed... -----Original Message----- From: George Abraham [mailto:[EMAIL PROTECTED] Sent: Thursday, June 29, 2006 7:51 AM To: CF-Talk Subject: Re: SOT: XML storage of metadata in database fields On 6/29/06, Tom Chiverton <[EMAIL PROTECTED]> wrote: > > On Thursday 29 June 2006 11:09, George Abraham wrote: > > We have an application that allows users to specify (at initial > > setup > time) > > Why not just add the users choice as columns ? Tom, If each user was allowed to specify their metadata fields, wouldn't we land up with a huge number of fields, most of which would be empty? Or am I understanding you wrong? Thanks, George ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:245061 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
