This document is archived and information here might be outdated. Recommended version. |
Provides access to members that control the Field Checker.
IFieldChecker has methods for validating fields collections and table names for a specific workspace. It's strongly recommended that this interface be used prior to two types of operations:
The main difference between these two cases is that while setting the ValidateWorkspace property is required to validate in either case, setting the InputWorkspace property is only required for the second case.
The Validate and ValidateField methods are responsible for verifying that field name, data types, and other parameters meet a minimum set of criteria that are required for the target workspace (set using the ValidateWorkspace property). ValidateTableName is used to verify that a table's name is not a reserved word, and that it does not start with or contain any invalid characters.
Name | Description | |
---|---|---|
InputWorkspace | Input workspace of the fieldchecker. | |
Validate | Checks the validity of a list of field names. | |
ValidateDictionary | Fieldchecker dictionary. | |
ValidateField | Checks the validity of a field. | |
ValidateTableName | Checks the validity of a table name. | |
ValidateWorkspace | Workspace of the fieldchecker. |
Classes | Description |
---|---|
FieldChecker | Checks for errors in Field Name. |
The logic used to determine if the OID field should be renamed to "ObjectID" can be classified with 4 cases.
Case1: Both the InputWorkspace and ValidateWorkspace are provided.
Case2: Only the InputWorkspace is provided (the ValidateWorkspace has not been provided).
Case3: Only the ValidateWorkspace is provided (the InputWorkspace has not been provided).
Case4: Neither of the workspaces is provided