If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

You can probably use a crosstab query with the labels defined as the column headers in order to create a new table.

But why do you think the current design is bad? The previous developer may have had a good reason for designing the table that way. It makes it very easy to add new attributes to the database without having to change the schema. For instance, to add an attribute called "color" you just add it to the current records with the label "color". With the attributes as individual fields, you will need to add a new field and possibly modify a lot of existing code to handle it.

Your data does not support what you are trying to do. For instance, IPage "Summary = 1H-P3500" has three "Communication Port" labels. How are you going to fit these into a single field? I really think the person who designed this schema used this table format for a reason.