I'm not that familiar with DBCX but an EAV structure would be something along the lines of;

Field        Meaning
TablePK      PK for EAV table
OwnerName    What table is that owner or parent for this record?
OwnerFK      FK to owner table
AttTypeFK    FK into AttType table to identify what this attribute is
AttValue     The actual value for the attribute uaually kept as char so that multiple datatypes can be supported.

Structures will vary from one implementation to another.



>DBCX being an implementation of same, right?
>
>Hank
>
>>>Does somebody else tried to implement Entity-Attribute-Value (EAV) model with VFP? Or it is better to go with XML if I need something more flexible than flat tables?
>>
>>Anton,
>>
>>Yes I have experience using E-A-V in VFP although we are using SQL Server for the data store but it doesn;t make that much difference. What is giving you problems?