You should use caution when adding attribute values listed in the Table View. The numbers in the table are NOT dynamic. This means if the geometry changes, lengthen a shapefile line or shorten a shapefile line, the value in the table will remain the same. This is in contrast to a line or polyline in AutoCAD where line length is immediately reflected in the PROPERTIES PALETTE.
To make the shapefile's table data consistent with the new length after a line is modified, you'll need to edit the value, or the length, directly in table's cell. Again, the Table Values are static, not dynamic.
To alleviate this, you may use MAPIMPORT command to import the shapefile. The Mapimport command will turn the shapefile geometry, or the ESRI entity, into AutoCAD entities, i.e. lines, polylines or points. The import procedure will be geospatially accurate and can 'hold' or maintain the dbf as OBJECT DATA. If you import it correctly, you can see the object data, abbreviated OD, at the bottom of the properties palette when you select an imported entity.
If the original author of the shapefile has made changes to the line lengths without making the appropriate edits in the table (or the dbf file) then the lengths listed in the table will not be accurate.If the original author is not aware that an office colleague has made a change to the shapefile line length, then the colleague should make an edit to the dbf file to reflect the new length of the line.
Chicagolooper
