Stores the row.
[Visual Basic 6.0] Sub Store
[Visual Basic .NET] Public Sub Store ( _ )
[C#] public void Store ( );
[Java] public void store ( ) throws IOException, AutomationException
[C++] HRESULT Store( void );
-2147216556 - FDO_E_OBJECTCLASS_REQUIRES_AN_EDIT_SESSION
When Store is called on a network feature when the data is unversioned or an edit session has not been started.
- 2147215606 - FDO_E_CANNOT_SET_WEIGHT_FIELD
When Store is called on a network edge feature with a weight field associated with Shape_Length, on unversioned data or when an edit session has not been started.
-2147217387 - FDO_E_FEATURE_NO_GEOMETRY
When Store is called on a network feature or feature in a topology with empty geometry.
-2147155573 - SDE_E_SE_STATE_CLOSED
When Store is called on a feature in a versioned feature class within an edit session, but outside of an edit operation. The error description returned will be "The requested operation is invalid on a closed state [name of class]"
The Store method is called by an application once it has modified the values of a Row. Once Store is called on a Row object, all subsequent queries within the same edit session, using the Geodatabase API, will reflect the modified state of the Row object.
All edits to features that participate in a Topology or Geometric Network must be performed within an edit session and bracketed within an edit operation.
Calling the Store method triggers the following actions:
- The IRowEvents::OnChanged is called for the row being stored. The OnNew is called if this is a newly created row being stored for the first time. A custom row object can implement the OnChanged method and take some special action when it is called - for example; update a special column in the row
- The IRelatedObjectEvents::RelatedObjectChanged method is called for related objects in a related object class if the table for this row is an object class that participates in relationship classes with notification
Store should not be used for batch operations, such as updates or inserts. For performing a number of inserts or updates using cursors, refer to the ITable::Insert, ITable::Update, ITable::UpdateSearchedRows , IFeatureClass::Update andIFeatureClass::Insert. If an insert or update cursor is used on non-simple features (such as network features), the cursor will revert to using Store.
It is not necessary to explicitly call Connect on network features, this is handled polymorphically when Store is called on the feature. This is also the case with features in a Topology, Dirty Area creation is handled internally when Store is called.
Store should not be called inside of edit events, such as OnCreateFeature, OnChangeFeature or OnDeleteFeature. Even if you are modifying the geometry or other field values, Store will be called once the event is complete.