2011

Table Of Contents

and column names when you define a new schema. You cannot map to an

existing table.

If you are mapping to an existing table or view in another data store (page

2059), make sure all column overrides correctly map to existing columns. If you

map to a table or view with a different owner, have the owner of that table

grant access to the FDO data store. You can create a local view that selects

from the other table, and map to the local view, but this may not be necessary.

The local view is created automatically if it is not present when you apply

your changes.

If you are mapping to a table and column in the current data store that does

not yet exist, make sure that the column name is valid for your database.

You must create schema elements hierarchically: create the schema first, then

its

feature classes (page 2063), and then its properties.

For feature sources from some FDO Providers, you can create multiple schemas

within the same feature source and change (page 610) the schemas after you

define and save them the first time.

You can view (page 608) a schema from any FDO Provider, but you cannot edit

or delete it if there are existing features that use it.