Best practice

HI all,
I'll try one more time, if no answer then I gather no one has an opinion
either way.
I have a claims database, which has a header table, details table and
otherinfo table. The header table will contain claim header info, ie
claimnumber date of loss etc., the details would contain claim detail, as
details of loss, damage ammounts, etc, the otherinfo contains information
not common to all classes of claims, so I would have a motor table
conmtaining driver, motor type model etc, GPA, would contain empoyee name,
earnings medical etc.
Now this is just in pricipal, hence no ddl, but anyway, some one suggested
that for the otherinfo table I create a descriptor table that will enable us
to add numerous columns for this "otherinfo" information at will
his quote is:
"descriptor table that can hold the field names, the data type, an input
string regular expression, and a bit field for required or not. Field Start
Date, and Field End Date. Fields can then be added and removed at will"
Whyle this might sound good, my gut says its a bad idea, for starters, it
could be a nightmare trying to create stable reports, etc.
Any other thought here or suggestions
Thanks
RobertHey Robert,
Stay on topic. I'll respond to your question in the original thread;
don't hijack a post.
Stu|||my apologies, did not try and hijack this topic. Musta done something
unintentional
Robert
"Stu" <stuart.ainsworth@.gmail.com> wrote in message
news:1144839162.136998.282480@.g10g2000cwb.googlegroups.com...
> Hey Robert,
> Stay on topic. I'll respond to your question in the original thread;
> don't hijack a post.
> Stu
>