First, multi value table fields are to be avoided. It is something you can create, but that doesn't mean you should. This design saves casual users from having to learn proper table design and relationships. The table that provides the mvf list is a hidden table that you cannot see, and I only know one person who might even know where it is (and he would never use them either). So forget about populating it with your list items. Instead, learn proper db normalization and ditch the mvf in your table. You will only have issues with it down the road.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.