Sergey's code simply takes out all numbers, assuming that letters are the size that you want. For this reason, I would seriously consider his other suggestion, to keep the size in a separate field. Then, you can either ORDER BY BASECODE, SIZE, or ORDER BY SIZE, BASECODE, depending on your needs. And, you don't have to parse (separate) the pieces - with the item codes you show, this part seems quite tricky.
I would keep the part that is not related to the size in a field BASECODE, and the size in a SIZE field; the PK (1) would be the combination of both.
(1) If you choose to use PKs with business value.
>Hi Sergey
>
>it does'nt work with this item
>HRN14421BLK0L
>HRN14421BLK0M
>HRN14421BLK0S
>HRN14421BLKXL
>HRN14421HGY0L
>HRN14421HGY0M
>HRN14421HGY0S
>HRN14421HGYXL
>
>TIA
>Ryan.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
