the data type of a value column in a row-modelled table is pre-determined, whereas in an EAV table, a value's data type depends on a attribute recorded in a particular row.
EAV Tables and Access
-
- 4StarLounger
- Posts: 528
- Joined: 26 Jan 2010, 15:14
EAV Tables and Access
I find it difficult to get my head around the EAV data model concept. Can I have an example of a table that uses such concept?
-
- Administrator
- Posts: 78488
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
-
- Administrator
- Posts: 78488
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: EAV Tables and Access
Here is a very simple example (tables only): questionnaires with questions with different response types.
You do not have the required permissions to view the files attached to this post.
Best wishes,
Hans
Hans
-
- 4StarLounger
- Posts: 528
- Joined: 26 Jan 2010, 15:14
Re: EAV Tables and Access
It does mention understanding the EAV model does require time
Have you ever used this data model in Access applications?
Have you ever used this data model in Access applications?
-
- Administrator
- Posts: 78488
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: EAV Tables and Access
Yes, in my previous job I built an actual questionnaire database using EAV.
Best wishes,
Hans
Hans
-
- 4StarLounger
- Posts: 528
- Joined: 26 Jan 2010, 15:14
Re: EAV Tables and Access
"the data type of a value column in a row-modelled table is pre-determined, whereas in an EAV table, a value's data type depends on an attribute recorded in a particular row"
You can actually see that being the case in your tblQuestion and it's interesting that you use the LookUp tab to represent a table column whose data type can vary because normally table fields data types are set in design view.
You can actually see that being the case in your tblQuestion and it's interesting that you use the LookUp tab to represent a table column whose data type can vary because normally table fields data types are set in design view.