2011

Table Of Contents

To help you maintain the integrity of your original data, a few limitations

apply when editing joined data:

■ When you edit a feature layer that has a

one-to-one join (page 2070) in the

Data Table, you can change the native feature data (from the primary table)

but you cannot change the joined properties (from the secondary table).

To edit the joined data, display Map Explorer, expand the data source

containing the table to edit, select that table, and click Table.

NOTE You cannot add or delete records from an ODBC data source using the

Data Table. Use the source application, for example Microsoft Access, to do

this.

■ For one-to-one joins, you can delete records from the primary source only.

You cannot edit one-to-one inner joins.

■ You can insert records in the primary source for a

left outer join (page 2066).

You cannot do so for an

inner join (page 2065), because the lack of a matching

secondary record would make the feature disappear.

■ You cannot edit inner joins or one-to-many joins. To make changes, you

must open the table itself from Map Explorer.

■ In general, you cannot edit primary keys.

Each feature class has a property whose value uniquely identifies each

feature within that class. This is called the primary key. Many feature classes

use a single property for this purpose, for example, FeatureId. However, a

feature class could have a list of properties such as street number, street

name, and street type to uniquely identify a house address.

FDO provider (page 2063) may also support the concept of autogenerated

ID values. When you add objects to your map using such a provider, the

identity property will not have a value, but it is still the primary key.

■ When working offline (page 721), the above rules apply, and you cannot

insert records at all.