Latest Contributions by AlexanderGray

You pMap variable is not strongly typed, that means it gets the type of the variable you are passing in (an IActiveView.)  This would work but is still bad: dim pMap as IMap = My.ArcMap.Document.ActiveView It is bad for several reasons.  1.  it won't work with Option strict on (which would flag the first problem.) 2. It won't work if you are in layout view in ArcMap, since in LayoutView, the ActiveView is a PageLayout (Map and PageLayout implement IActiveView.  The document has a maps method which is a collection of the maps in your document (there may be more than one.)  You can pick the first but it may still be incorrect.  I like using the IMxDocument.FocusMap.  If you are in data view, you get the map loaded into view, if you are in layout mode, you get the map which is selected on the page layout. ... View more

Yes, there a lot of things kind of strange with this forum...  People posting questions and then posting an answer and marking their own post as the answer post.  However, the points are browny points anyway and the value comes from the users not from the points. As far as getting the correct layer, yes the code you posted should work as long as you have the option strict off (which I don't recommend.)  Option strict forces you to explicit cast (type conversion) to the specific type before you pass in an argument to a method.  In your case, your method signature calls for an IFeatureLayer.  Your method passes in an ILayer.  That works fine as long as the ILayer happens to be a FeatureLayer.  All FeatureLayers implement ILayer but lots of other types of layers implement ILayer such as grouplayer, rasterlayer, etc. and don't implement IFeatureLayer.  Explicitly casting your ILayer to IFeatureLayer is a better practice. Dim fLayer as IfeatureLayer = ctype(pMap.Layer(0), IFeatureLayer) SelectMapFeaturesByAttributeQuery(pMap.ActiveView, flayer, "PID = '00000000'") Now there is always the chance the first layer in the map is not a featurelayer, in which case the first line would fail if typeof pMap.Layer(0) is IFeatureLayer then   Dim fLayer as IfeatureLayer = ctype(pMap.Layer(0), IFeatureLayer)   SelectMapFeaturesByAttributeQuery(pMap.ActiveView, flayer, "PID = '00000000'") End if or better yet, trycast returns nothing if the cast fails Dim fLayer as IfeatureLayer = trycast(pMap.Layer(0), IFeatureLayer) if fLayer isnot Nothing then   SelectMapFeaturesByAttributeQuery(pMap.ActiveView, flayer, "PID = '00000000'") end if You can write a for loop to go from 0 to pMap.LayerCount -1 and look at the layer of featureclass name.  However, if you hit a group layer, it will be skipped and you will never look at the sub layers and also the code will crash if your map is empty (you can check the layercount before calling.)  I prefer to use the IMap.Layers method. Dim featLayerUid As New UIDClass featLayerUid.Value = "{40A9E885-5533-11D0-98BE-00805F7CED21}" 'IFeatureLayer Dim enumLayer As IEnumLayer = pMap.Layers(featLayerUid , True)  'True argument looks at sub layers in a group enumLayer.Reset() Dim layer As ILayer = enumLayer.Next Do While Not (layer Is Nothing)       dim fLayer as IFeatureLayer = CType(layer, IFeatureLayer) 'Guaranteed to work since only querying IFeatureLayers.       if ctype(fLayer.FeatureClass, IDataset).Name = "Name_I_am_looking_for" then            SelectMapFeaturesByAttributeQuery(pMap.ActiveView, fLayer, "PID = '00000000'")            exit do       end if       layer = enumLayer.Next() Loop    ... View more

what controls do you have on the dockable window?  Do these controls reference assemblies not on the target?  Do you have exception handling on all your events in the dockable window?  If so you should be able to handle the exception and write out the message. ... View more

The code provided by Ken is vb.net not vba, so for a c# add-in it is the same just with a c# syntax http://www.harding.edu/fmccown/vbnet_csharp_comparison.html if this is a not an add-in and is a tool inheriting basetool, you just have to override the Enabled property of the basetool and put whatever code you need in there as long as it returns true or false.  Hint, don't put code too elaborate in the enabled property because it runs basically all the time (ie on mouse move.)  If the tools or commands need to talk to notify each other, I suggest adding an extension to the mix and setting and reading values on the extension.  There can be more than one instance of a command or tool in arcmap which will lead to confusion over where the value is set.  There can only be one extension with the same classid loaded at one time making a unique repository for values that need to be passed around. ... View more