The data is normalized, although I understand why one might think it is not. But you make a good point about the field length hitting the limit of 254 char. So I have to rethink the strategy of displaying the fields. Thank you for your input and suggestions.
>Hmmm...without knowing any details of the application, my first opinion is that these should not be in 16 fields, but in a separate table (related to the first), containing one record for each piece of equipment. Sounds like your data is not properly normalized.
>
>Another problem with your scheme is that it will crash when you hit 13 fields...255 (or 254?) character limitation per field...unless you are trimming the fields).
>
>How would you split this to rows once it got to the report?
>
>>Yes, so that I can place this field on the VFP report. And then the report will print each equipment name on a separate line. And there will be just as many lines/rows as selected equipment.
>>
>>>And your goal is to have one very long field that contains all of those results, separated by semi-colons?
>>>
>>>>Yes, EQ1NAME .. EQ16NAME are fields in a table.
>>>>
>>>>>Just to be clear...is EQ1NAME the name of a field that exists in the table? IOW, it is not a variable that contains the name of a field.
>>>>>
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
