IMapServer3.QueryRelatedRecords Method

Returns the IDs of the rows that meet the query filter selection criteria for the specified table.

[Visual Basic .NET]
Public Function QueryRelatedRecords ( _
    ByVal MapName As String, _
    ByVal sourceTable As Integer, _
    ByVal pFIDs As IFIDSet, _
    ByVal RelateDescription As IRelateDescription _
) As IQueryResult

[C#]
public IQueryResult QueryRelatedRecords (
    string MapName,
    int sourceTable,
    IFIDSet pFIDs,
    IRelateDescription RelateDescription
);

[C++]
HRESULT QueryRelatedRecords(
  BSTR MapName,
  long sourceTable,
  IFIDSet* pFIDs,
  IRelateDescription* RelateDescription,
  IQueryResult** ppQueryResult
);

[C++]

Parameters
MapName [in]
  MapName is a parameter of type BSTR
sourceTable [in]
  sourceTable is a parameter of type long
pFIDs [in]

  pFIDs is a parameter of type IFIDSet
RelateDescription [in]

  RelateDescription is a parameter of type IRelateDescription
ppQueryResult [out, retval]

  ppQueryResult is a parameter of type IQueryResult

Product Availability

Remarks

When esriRelateResultRelatedRecordSetAsObject is selected as ResultFormat, the function returns RelatedRecordSet embedded within a QueryResult. Use QueryResult.Object to get RelatedRecordSet.

An FIDSet needs to be created and assign an array of ObjectID to FIDArray property. Related records for ObjectID(s) contained by FIDSet will be queried. Typically this function follows QueryData, in that case you can use values of OIDField from the returned RecordSet to populate FIDSet.

RelateDescription contains information about relationship that will be explored. RelateDescription needs to be created and populated with relates ID, list of fields and output result format. In case where both RelatedTableFields and IncludeGeometry is set, RelatedTableFields takes precedence over IncludeGeometry. For example, when RelatedTableFields=“Shape, FName, LName, Address” and IncludeGeometry=False, the output recordset will contain geometry as contained within the Shape field.

When more than one ObjectID is passed, use SourceRowID to relate ‘related rows’ back to the source feature or row.

The result honors the fields visibility set in the layer or the standalone table.

Output Spatial and Time Reference

If the desired spatial reference of the output geometry is different than the original one, OutputSpatialReference should be used. Otherwise geometry is returned in the same spatial reference system as the DefaultMapDescription by default.

Values in StartTimeField or EndTimeField are returned in the Layer's TimeReference. If the desired time reference is different than the layer's one, OutputTimeReference should be explicitly set.

Relates with non GeoDatabase Tables

Since QueryRelatedRecords relies on IDs of features or rows from the source layer/table, when a table does not have an OIDField (not a Geodatabase table), finding related records from the source layer/table from the destination table is not possible. For example, when a Parcel layer is related to a Owership table (for example from an Oracle database), you may find related ownership information for a parcel, but the function does not allow to find parcels belong to a owner. In order to traverse the other way a table must have a OIDField. You may consider one of the following options for this type of scenario:

• Import the table in your Geodatabase
• Use QuerLayer in ArcMap to add the table as a non-spatial table with user defined unique idetifier fields.
• Create a unique, not null, indexed numeric field in your OLE DB table and the field will be recognized as a pseudo ObjectID field. Please see these KB articles (id: 20463, 27424) for more information.

Please note that retrieving related rows that has joins may impact the performance.

See Also