The best suggestion is "don't".
Always store values as the most appropriate type: which means that numbers get stored in numeric columns, dates in DATETIME columns, and so on.
And when it comes to sequences of numbers, storing them as comma separated values is nice and simple to do for the initial insert, but quickly becomes a major PITA to do anything useful with. As you are starting to see! Now imagine that you need to change "1850100" to "1850275" later on - and think what a difficult, clumsy and generally awkward job it is.
Instead, change your DB to use a second table which correlates a sequence number to a SR_NO and use SQL to retrieve them. It's a little more difficult to set up initially, but it will save you a serious amount of time later.
But if you think must keep a very bad database design then this:
Converting comma separated data in a column to rows for selection[
^] will show you how to do this task - and you might change your mind! :laugh: