Data output sequence when running a query

[SLT2195]

Why would 010322-01 output before 092521-01 in a query when the field is sorted ascending?

[June7]

Because 01 comes before 09. Why would you expect otherwise?

[Welshgasman]

Go on, I'll bite.
Why would you think otherwise?

[Micron]

The values are obviously text, so once that question is figured out, it might come as a surprise to OP that
111
comes before
22

[SLT2195]

It is a "short text" field currently, but would it be possible to alter a parameter to cause it to act as if this were a number with 010322-01 being larger than 092521-01?

[Micron]

act as if this were a number with 010322-01 being larger than 092521-01?

you still think that 10322 is larger than 92521? Why? Ten thousand + some hundreds will never be larger than 92 thousand + some hundreds??
IMO, your only probable solution to get what you want is to either
- add a sort field & assign real numbers to these values in the order you want. I'd increment by 5's or 10's not 1's OR
- split the parts into real numbers and concatenate the parts in your forms/reports/queries

[orange]

would it be possible to alter a parameter to cause it to act as if this were a number with 010322-01 being larger than 092521-01?

No.

Depending on your application, you might consider a "Sequence" field to allow sorting.

[SLT2195]

Found a workaround. Will sort on a "date" field before sorting on the "work-order number" field in the queries. This seems to provide the required results. Thanks to everyone. Yes, I have a lot to learn.

[orange]

Always better for communication and more focused responses when the issue is presented in context. Happy to hear there was a "date" field available for sorting.