Working with SDE layers with Multi-entity typesApplies to: MapObjects 2.0, SDE users
If you create a layer which contains more than one entity type, i.e. Polygons and Lines, then the recordset of the layer will contain all of the layer's records (i.e. Lines and Polygons). This is the behavior at both MapObjects 1.2 and MapObjects 2.0.
For example, let's say you've created an SDE layer
MapObjects 1.2 vs. 2.0 and multiple-entity types with SDE
One of the differences between MapObjects 1.2 and 2.0 occurs when you access the value of the "Shape" field for a record which does not contain the expected entity type for that layer, such as returning the value of a line record in a polygon-defined theme. For example, using the following code
in MapObjects 2.0, an error will be generated if the layer was defined as MYUSER.MULTIGEOM.SHAPE.POLYGONS, whereas with MapObjects 1.2, it will simply return nothing. This is due to internal changes in the way that MapObjects 2.0 handles NULL shapes and is not affected by the Visual Basic definition of the pLine object -- that is, dimensioning the pLine object as an Object rather than a MapObjects2.Line will not matter.
Ideally, MapObjects should only return those records which are of the specified type for the layer and this is something which we will be looking at for a future release. However, in the meantime, we suggest a workaround. Basically, we want to filter out only those features which are of the required entity type for our layer. To do this, we can user the FilterExpression method to narrow down the layer. For this, we need to have a field on which we can query, a field which describes the entity type for that record. However, no such field exists by default, in the layer's Business table in SDE. As a result, two options are available:
A) To amend the business table to include a field that declares the entitry type for each record and use this for the layer's filter expression. For example:
This first option is perhaps simple to implement but has many disadvantages, such as maintaining the integrity of the data, etc.
B) Join to the layer's FTable and query the value of its Entity Field in the filter expression. This requires the following steps:
Some Visual Basic code to implement the above:
 Create a temporary recordset based on the SDE.LAYERS table and extract the required layer_id. The following code snippet hard-codes the layer name, but this can easily be parsed from a ListBox, etc.
 Create your SDE data connection as usual. Once that is done, define your filter expression - this is the SQL statement that you will need to effectively join the F table. Note that the IN clause should be supported by most RDBMS'. This SQL statement has been hard-coded for entity type 8 = Polygons. (2=spaghetti lines, 1=points etc.)
(4) Retrieve your records
This will now only return records that are polygons, so long as sLayerName = "MO2DEV.MULTIGEOM.SHAPE.POLYGONS"