numbering order in schedule

[Anonymous]

this has probably been dealt in another thread but haven't found it...

i've created a schedule to list storage unit names, floor levels and ceiling heights; in this case, the units are numbered 1 to 49 and i've set the zone names as such.

when open schedule, the unit names are listed as such: 1,11,12,13,14,15,16,17,18,19,2,21,22,23......
.......38,39,4,41,42......49,5,6,7,8,9.

very frustrating; i can't seem to figure out how to get the names to list sequentially.

any advise would be welcome.

thanks in advance,

rob

[Piotr Dobrowolski]

Which version?

I noticed that corrction of Your problem is one of the so called "small improvements" in 11.

Best Regards,
Piotr

[Barry Kelly]

BN_kombibob wrote:
this has probably been dealt in another thread but haven't found it...

i've created a schedule to list storage unit names, floor levels and ceiling heights; in this case, the units are numbered 1 to 49 and i've set the zone names as such.

when open schedule, the unit names are listed as such: 1,11,12,13,14,15,16,17,18,19,2,21,22,23......
.......38,39,4,41,42......49,5,6,7,8,9.

very frustrating; i can't seem to figure out how to get the names to list sequentially.

any advise would be welcome.

thanks in advance,

rob

Technically they have listed sequentially.
Is it possible to number your units 01, 02, 03, ....., 09, 10, 11, 12, ....etc.

Barry.

[Anonymous]

thanks barry, that's a good simple workaround i'll try it out...

will follow up v11 "improvements" as that is what i am using.

rob

[Anonymous]

Hi,

This faulty numbering order is a strange issue if you think that some guys went to the moon 40 years ago? With calculation like this they would still be 'on the way' .

We usually put a dummy ordering parameter first - the height to project origin - so the floors are ordered despite their name. The printable width of this field is set to zero.

[Djordje]

IMHE all software will do this ...

[James Murray]

The Finder handles it correctly.

[Anonymous]

Graphisoft calls the zone text field #2 as 'Zone number' so suppose it should behave like one? It can't handle the natural sort order even in the split mode. Bug, not a feature (IMHO).