A feature data object (FDO) such as a shapefile does not behave like plain vanilla AutoCad objects. When you move the vertex or side of a vanilla rectangle, the change is reflected in the Properties palette right away. An FDO doesn’t behave like that.
Although a shapefile’s record (a row in the table is a record) is associated with the geometry, the data itself is static, it won’t change. The only way a record’s value will change is when you manually edit it. This means when you edit the vertex of a polygon to make its area smaller the area in the table must be edited too. After the edits to both the geometry and table have been made, you must perform ‘check-in’ so your changes are confirmed and rewritten to the shapefile’s geometry and recorded in the database.
If you just change the geometry without making edits to the database then that record’s data will be inaccurate. Incorrect data in your table will also lead to inaccurate results if your analysis relies on that data.
Chicagolooper
