The short answer is 'no'.
The long answer is that multivalued fields are a bad idea in relational database design. In db normalization nomenclature they are called "repeating groups", and a table that contains repeating groups is not even in first normal form (1NF). The definition of first normal form is, essentially, "no tables in your schema contain repeating groups." Ideally, all of the tables in your db schema should achieve at least 3rd normal form. Normalization aside...
The way to handle your multivalued field (e.g., multiple telephone numbers) is to remove it from your primary table and place it in a new table that has a one-to-many relationship to your primary table (e.g., Clients). Add a forieng-key field to your new table (many-side of the relationship) that relates to the primary-key field of your primary table.
If you want to list your related multiple values, use a query to bring them together.
Hope that makes some sense.
Bob
|