Is this a trick question? ;)This is one of those times where the docs just reiterate what the method is called. It "draws the foreground"... ok... but.... http://help.arcgis.com/en/sdk/10.0/java_ao_adf/api/arcobjects/com/esri/arcgis/carto/esriViewDrawPhase.htmlah.. .but wait. Did you see the "see also" part?In an ActiveView is has this info:http://help.arcgis.com/en/sdk/10.0/java_ao_adf/api/arcobjects/com/esri/arcgis/carto/IActiveView.html#partialRefresh(int, java.lang.Object, com.esri.arcgis.geometry.IEnvelope)In a Map it's unused, in a Layout it is snap guides.
How are you doing the join? We use unique value renderers on layers with joins all the time and have never had any problems. If you are creating the join through code using IMemoryRelationshipClassFactory.Open then check the order of the parameters. The originPrimaryClass parameter should be a reference to the table and the originForeignClass parameter should be a reference to the feature class. I've seen many cases where people were passing these references in backwards and, while it does perform a join, it joins the layer to the table instead of joining the table to the layer. This causes several things to not work correctly in ArcMap and I would presume affect ArcEngine applications as well.
geoFeatureLayer.FeatureClass = relQueryTable as IFeatureClass;
Dim memRelClassFactory As IMemoryRelationshipClassFactory
Dim relClass As IRelationshipClass
Dim displayRelClass As IDisplayRelationshipClass
memRelClassFactory = New MemoryRelationshipClassFactory
relClass = memRelClassFactory.Open("Join", CType(table, IObjectClass), tableField, featureLayer.DisplayFeatureClass, layerField, "forward", "backward", esriRelCardinality.esriRelCardinalityOneToMany)
displayRelClass = CType(featureLayer, IDisplayRelationshipClass)
Retrieving data ...