"I see this in more than just ORD. Windows does this at times as well. But I would like to see it too!
Sorting sometimes is not looking at the entire word or string, but sorting the first character of each entry, then the second, etc. That is why we get P1, P10, P11, P12, --- P2, P20, etc.
Without getting Microsoft to change as well, should be easier to have ORD 'pad' the numbers with 0's for sorting, just need to be able to choose your desired number of digits in the software (or in Civil settings, like a decimal accuracy). Then you would get a list of P001, P002, P003, --- P010, P011, --- P100, P101, etc."
I agree as well, though the issue may be more than just Bentley. I commented on a similar idea in Civil Ideas.
BCI-I-1047
"I see this in more than just ORD. Windows does this at times as well. But I would like to see it too!
Sorting sometimes is not looking at the entire word or string, but sorting the first character of each entry, then the second, etc. That is why we get P1, P10, P11, P12, --- P2, P20, etc.
Without getting Microsoft to change as well, should be easier to have ORD 'pad' the numbers with 0's for sorting, just need to be able to choose your desired number of digits in the software (or in Civil settings, like a decimal accuracy). Then you would get a list of P001, P002, P003, --- P010, P011, --- P100, P101, etc."
Couldn't agree more!
Current workaround is to use leading zero's in the (string) property. So 060mm instead of 60mm => then it will sort correct.