Latest Contributions by EdwardBlair

Hello - I'm trying to copy/paste a File Geodatabase into an Oracle SDE Instance running in Windows 7.  There are 61 classes in the FGDB.  When it hits about the 6th class I get the error: Failed to paste <dataset> Underlying DBMS error From there I'm trying to find out what kind of error was encountered.  I've looked in the Windows Event Viewer but can't find anything there.   Is there another location where I could find more details about the error? Thanks, Ed ... View more

Hello ??? I???ve got a process that???s built in C# using ArcObjects v10.1 that reads data from a feature class in a source File Geodatabase, applies updates to attributes and sometimes the shape, and writes a new feature to a target feature class in another File geodatabase.  This works fine.  As a typical example in one case it reads and writes about 120,000 features in 4 minutes. Now I need to update the process to write to an Oracle SDE instance.  Overall it works, its just much slower.  For example, the process that took 4 minutes to process 120,000 records in an FGDB takes 18 minutes in Oracle.    This alone would be OK.  My issue is that I???ve got some processes that take hours in the FGDB. As part of the updates for Oracle I???ve switched to use of IFeatureClassWrite::Write instead of IFeature::Store that I was using in the FGDB.  My understanding is that the FeatureClassWrite doesn't trigger events like Store.  However this doesn???t seem to make much difference.  Here???s an overview of what the process does. // Get the target workspace IWorkspace targetWorkspace = workspaceFactory.OpenFromFile(connectionString, 0); IWorkpaceEdit workspaceEdit = (IWorkspaceEdit) targetWorkspace; // Start editing workspaceEdit.StartEditing(false); workspaceEdit.StartEditOperation(); // Open the source and target feature classes IFeatureWorkspace sourceFeaWorkspace = (IFeatureWorkspace) sourceWorkspace; IFeatureClass sourceClass = sourceFeaWorkspace.OpenFeatureClass(sourceClassName); IFeatureWorkspace feaWorkspace = (IFeatureWorkspace) targetWorkspace; IFeatureClass targetClass = feaWorkspace.OpenFeatureClass(targetClassName); IFeatureClassWrite fcWrite = (IFeatureClassWrite) targetClass; // Put the target class in load-only mode and apply a schema lock IFeatureClassLoad fcLoad = (IFeatureClassLoad) targetClass; ISchemaLock schemaLock = (ISchemaLock) targetClass; schemaLock.ChangeSchemaLock(esriSchemaLock.esriExclusiveSchemaLock); fcLoad.LoadOnlyMode = true; // Read from the source and write to the target IFeature targetFea = null; IQueryFilter queryFilter = new QueryFilter(); IFeatureCursor feaCur = sourceClass.Search(queryFilter,true); IFeature sourceFea = feaCur.Next(); while (sourceFea != null) { [INDENT]targetFea = targetClass.CreateFeature(); // Update the shape and attributes // Store the target feature    fcWrite.WriteFeature(targetFea);         sourceFea = feaCur.Next(); [/INDENT] } // Stop editing and release lock workspaceEdit.StopEditing(true); schemaLock.ChangeSchemaLock(esriSchemaLock.esriSharedSchemaLock); fcLoad.LoadOnlyMode = false; I???ve also tried grouping features into an ISet and using IFeatureClassWrite::WriteFeatures.  No difference in performance.  I???ve also tried using an InsertCursor.  No difference in performance. Is it just the case that writing directly to an Oracle SDE instance is 4 to 5 times slower than writing to an FGDB?   Any insights or suggestions at all would be much appreciated. Thanks, Ed ... View more

I've got a case where a line feature class is the destination of a one-to-many relationship and has an integer foreign key field named (for simplicity's sake) "ForeignKey".  When this is split by an edit operation I want both new lines to retain the same relationship to the original parent, so I created a range domain named "DuplicateForeignKey" with a split policy "Duplicate".  Hope was that the value in the "ForeignKey" would remain in both new features after the split.  No so.   At least not so far in my testing.   Only one feature retained the foreign key value -- the longer one. My goal is to use the IFeatureEdit2.SplitWithUpdate method to do the splitting programmatically.  The ForeignKey was not duplicated as I'd hoped, so I tried the same operation using the Split tool in ArcMap.  Same results. I may be missing something basic here.  Any suggestions would be much appreciated. I'm working in ArcMap 10.1, ArcEditor licensing (I guess that's called "Standard" now.) Thanks, Ed ... View more

I've got a tool that needs to operate on a selected set of features in a layer.  It then needs to process a subset of the selected features based on a query filter.  This is straightforward.  For example: IFeatureSelection pFSel = (IFeatureSelection)pFLayer; ISelectionSet pSelectionSet = pFSel.SelectionSet; IQueryFilter pQF = new QueryFilter(); pQF.WhereClause = "MATERIAL = 'PL'; IFeatureCursor pCursor; pSelectionSet.Search(pQF, true, out pCursor); And pCursor holds the result. Now, what if the layer in question is a join layer. If I want to select from the join layer using a field in the joined table I can use SearchDisplayFeatures on IGeoFeatureLayer, as in: IGeoFeatureLayer pGeoFLayer = (IGeoFeatureLayer)pFLayer; pCursor = pGeoFLayer.SearchDisplayFeatures(pQF, true); Which works fine.  But if I want to subset an existing selection set using a query filter that references a field in the join table... well, I'm stumped.  Any suggestions would be much appreciated. Thanks, Ed ... View more

I recently completed a process where I built and tested a command in ArcMap using the ArcObjects SDK.  The command makes extensive use of objects in the Geodatabase, Carto and Geometry namespaces.  As is strongly advised I made sure all cursors created when querying the Geodatabase are released when the command is done with them (using Marshal.ReleaseComObject).  The command was tested extensively on other desktop machines and numerous issues rooted out. By the time it was to deliver to the client I was feeling pretty good. But the client had a Citrix application server.  And when the command was installed there we quickly discovered it to fail in ways it had never failed in all of our desktop testing. After multiple mis-diagnoses and considerable stress and strain we found that other COM objects needed to be released as well.  A particular case in point was this: (ISegmentCollection) segCol = (ISegmentCollection)curvePolyline; (IEnumSegment) polySegments = segCol.EnumSegments; int outPartIndex = 0; int outSegIndex = 0; int partIndex = 0; polySegments.Next(out polySegment, ref outPartIndex, ref outSegIndex); while (polySegment != null) {     switch (polySegment.GeometryType)     {          case esriGeometryType.esriGeometryLine:               // do stuff               break;          case esriGeometryType.esriGeometryPolyline:               // do stuff               break;          case esriGeometryType.esriGeometryCircularArc:               (ICircularArc) circArcPart = (ICircularArc)polySegment;               // do stuff              break;        }        polySegments.Next(out polySegment, ref outPartIndex, ref outSegIndex); } When this was altered to release the polySegment, polySegments and segCol objects on completion of the "while" loop and when the circArcPart object was released after use (and other similar changes) the code worked reliably. After the fact I heard from other developers that Citrix is, for whatever reason *way* more sensitive to COM object life span management than desktop applications. So..... my question is, what makes Citrix so sensitive?  And more importantly, are there guidelines for COM object management for Citrix that would supplement the general information ESRI provides on releasing COM objects? Thanks, Ed ... View more