Sergey,

Yes, #1 came to my mind. I already have a second table that holds a sizing matrix that is in the proper order, but the myriad of places that I would have to use this 2nd table would break too many things. Though I could add a second field to my existing main table and add the sortorder value to it on inserts via lookup ... hmmmmm

Option #2 I have to think about. I like the first option, it gives me something indexable other than 'size'. Thanks.

>I would create a table with two columns: Size C(5) and SortOrder I and use it for sorting. Another way is to store sizes in a string in proper order and use AT() as sortorder.

lcSizes = ",XS,S,M,L,XL,2XL,...,"
>? AT([,] + ALLTRIM(size) + [,], lcSizes)

>