That is not what a multi valued field is. A multi valued field has a single data type. The data appears concatenated when you view it, but in fact it is stored in a child table in a normalized manner. Basically it structures the data in the same way you would a child table, but it does it behind the scenes. Advanced developers may find that annoying, but novice users may like the ease.
You can see this demonstrated when using a recordset on a multivalued field
Assume you have a table with a multivalued field called "mv". In that field you have records like.
ID MV
1 red, blue, green
2 orange, yellow
3 red, yellow
dim rs as dao.recordset
dim rsChildren as dao.recordset
set rs = currentdb.openrecordset "tblOne"
Do while not rs.eof
set rsChildren = rs!MV.value
do while not rsChildren.eof
debug.print rs!ID & " " & rsChildren!fields(1)
rsChildren.movenext
loop
rs.moveNext
loop
This would print
1 red
1 blue
1 green
2 orange
2 yellow
Although you see this in the field when viewing it
red, yellow, blue
it is not a text "red, yellow, blue". It is in fact three seperate records. You can query
where MV = "red"
and it will return all fields with "red".
I am not that big into using them, because you are limited to the multi value combo box and text box and can not use traditional controls. However, there is some utility and need to be understood by advance access developers.
As I said the attachment field is a multivalued field. This has completely overcome bloating and provides a novice user capability that only advanced developers can deliver.