In ORD 10.11 and beyond the Best Match Field Code Option is now a drop-down of the following:

Match exact: Feature Must equal an Alpha Code, only exact matches. For example if there is a Feature Definition with Alpha Code set to AP (Asphalt Pavement) and the user has points in the field with Code AP, that is a match and points and Lines will be drawn with the properties of AP Feature Definition, but if the point in the field has a Code AP1, AP2, AP3, that is not exact match and the Codes will appear in Red in the explorer pane: AP1, AP2, AP3 meaning these Feature Definitions do not exist .

Match Start: Feature Must Start with Alpha Code. For example, if there is a Feature Definition with Alpha Code set to AP (Asphalt Pavement) and the user has points in the field with Code AP, AP1, AP2, AP3, APA, APB, APB1, APB2 the Best Match Feature Definition found will be AP and points and Lines will be drawn with the properties of AP Feature Definition .
Match Alpha: Feature must be alpha numeric and alpha part must equal an alpha code. For example, if there is a Feature Definition with Alpha Code set to AP (Asphalt Pavement) and the user has points in the field with Codes AP, AP1, AP2, AP3, the Best Match Feature Definition found will be AP and points and Lines will be drawn with the properties of the AP Feature Definition. NOTE: APB, APB1, APB2 will not work.

Match Truncate: Truncate Match to number of characters (feature is truncated one character at time until find matching alpha code with number of character minimum). For Example, If there is a Feature Definition name COLUMN and the point in the field has Code COLUM, with the N missing, it will be matched to the left one character at the time. This works in conjunction with "Best Match Truncate Value".

Match Exact won't work if you use string values

Match Start will work if you use string values. If you have a field code of 176(Edge of Pavement) and you use 176.1 or 1761 to assign a string value then the best match will be 176. However, if you accidentaly code 176.1 as 1176.1 or 11761, ORD will best match to 117 which in my case 117 is (Edge of Sidewalk). This might make finding this error difficult.

An enhancement for these types of sceanrios would be wonderful. Possibly another setting for how the software should address string values.