>What do you think? Thanks for a clue.

Looks like you got several suggestions that will get you going.

I would like to add, however, that without knowing the exact business situation you are trying to model, the table structure you are referring to looks suspiciously denormalized. ANy time you have that many fields that hold the same type of data, you should probably be looking at creating a child table with 1 record per field value. IOW, instead of having a parent table with 10 fields, one for the name of each of my children, you should have a parent table, and a child table with 10 records that holds the name of the child and a foreign key that refers to the parent.

You'll almost always find that when your data is normalized from the beginning, special coding requirements like the ones you have been asking about are not needed, and the routines to manipulate your data come much more naturally.