Hi and thanks for your replies,
Message for Andreas Sheriff ! : I did not understand your solution
completely but seems nice,would you please tell me more or direct me to
proper source?
And reply for Carlos: I think there is only one entity called "Form".This
is an conceptual modeling(not design) so there is no *Entity* called filed.
You can say that I map the original ER to a logial design with two tables
named by: Form and Filed. But this has the same problem with EAV method that
I have mentioned in original post.
-Thanks
Carlos wrote:
>My approach:
>
>Parent Entity 'Form' with attributes (like size, colour, etc...)
>and
>Child Entity 'Field' with relationship dependent to the parent entity
>plus Field Identificator with attributes heigth, width, X pos, Y pos,
>colour, prompt...
>
>With a design like this, you should be able to manage n forms with m
>fields within.
>
>HTH
>
>Cheers.
>
>Carlos.
--
Message posted via http://www.dbmonster.com
Received on Sat Dec 03 2005 - 06:00:53 CST
