ArcGIS Engine Q & A: Why cannot the element class of the same name be generated in the geographical database? arcgisengine

ArcGIS Engine Q & A: Why cannot the element class of the same name be generated in the geographical database? arcgisengine

The reason for such a problem is that no matter whether a element class is directly put in the blank question of work or a element data set of the blank question of work, these differences are only logical, their physical composition is a two-dimensional table in the database, and the table name is the name of the element class. Two two-dimensional tables with the same name cannot appear in a database, therefore, two element classes with the same name cannot be generated.

That is to say, if there is A feature class named A and A feature dataset named B in the work blank question, it will not succeed if another feature class named A is generated in B.

Therefore, you can use the IFeatureWorkspace: OpenFeatureClass method to open any element class in the work empty question, whether it is directly stored in the work empty question or a element data set in the work empty question.

What is the cause of failed element class creation in Arcgis geographic database (as shown below)

When the database is created, you must set the precision. The system will set the field based on the precision.

If you set a low-precision dataset, the domain will be large, and you will not be able to put high-precision data into it.
 
Why is there an error when I import element classes to the personal geographic database created in arccatalog?

I have also encountered this situation. I personally think that the personal geographic database of version 10.0 is not good enough to cause errors.
If you need to import the personal geographic database (in. mdb Format) or use 9.3, otherwise, you can use the File geographic database to avoid this problem, but the format is not. mdb.