Field Code Sort Order

[alarism]

There was a way in LDD that you could reverse the sort order on Description Key files with variable length field codes so that SSF* did not get caught in SS*, thus far I have been unsuccessful with finding this setting in C3D. Anyone have it?

[sinc]

You can create multiple Description Key Sets, and then set the order of the Sets. That should solve your problem, at the cost of needing to split your Description Keys into multiple sets (which might make management more annoying).

[alarism]

Ya I thought about that, but is seems like overkill since they had the setting in LDD, and it seems like a no brainer in terms of necessity.

[sinc]

We create our field codes in C3D, then dump them into the data collector. Now the field guys can type a character or two, then select the rest of the code from a list. They don't have to type the whole code.

Because of that, we've moved to longer, more-descriptive codes. This helps prevent incorrect coding in the field. And it also means that our points in C3D have better descriptions, which actually mean something to anyone who happens to be looking at our drawing. No confusion, no needing to puzzle out what a code means, even for people who are not with our company.

In addition to those benefits, that change pretty much eliminated the need to reverse the sort order of the keys. So it's something I haven't missed, and hadn't really even thought of until you posted your question.

[mjfarrell]

looks like less use of wild cards in the description would be the direction to take

[alarism]

You both make good points, without finding the reverse sort order setting we have 3 options:

1) Multiple Field Code Description Key files broken into number of characters per code and prioritized from longest to shortest.

2) Turn on space recognition.

3) Deal with it.

Options 1 & 2 were a consideration, but require a change in procedure. I was hoping to keep it simple by changing one system variable, but I guess that's not an option.

[dmo1205]

We create our field codes in C3D, then dump them into the data collector. Now the field guys can type a character or two, then select the rest of the code from a list. They don't have to type the whole code.

Because of that, we've moved to longer, more-descriptive codes. This helps prevent incorrect coding in the field. And it also means that our points in C3D have better descriptions, which actually mean something to anyone who happens to be looking at our drawing. No confusion, no needing to puzzle out what a code means, even for people who are not with our company.

In addition to those benefits, that change pretty much eliminated the need to reverse the sort order of the keys. So it's something I haven't missed, and hadn't really even thought of until you posted your question.

@Sinc
Can you point me to a tutorial on how to do this. It seems like it would save an amazing amount of trouble as the survey guys sometimes go EOP or EP for edge of pavement.
Thanks
Daniel