Bug:  Geodatabase attachments are not automatically included in the output of geoprocessing tools

【解决方案】
When a geoprocessing tool creates a new output from the feature class, as the Project (management) tool does, the attachments associated with the input feature class are not carried over to the output feature class. Here are a few steps that can be done to 're-relate' the attachment table that stores the attachments with a new output feature class.

These steps are only valid if the geoprocessing operation being performed does not reorder ObjectIDs (the Project tool DOES NOT reorder ObjectIDs). This can be tested by running the tool, then checking the output dataset — if each of the records in the input dataset have a corresponding record in the output dataset, and the ObjectIDs match, then use the steps below.

1. Run the desired geoprocessing tool, such as the Project (management) tool.
2. Right-click the output feature class and create/enable Attachments. This creates an empty __ATTACH table and a relationship class relating that table to the output feature class.
3. Use the Append (management) tool to append the original feature class' __ATTACH table into the output feature class' __ATTACH table. The __ATTACH table is where the attachments are actually stored (in a BLOB field), so appending these records is a key step. Input Dataset = input__ATTACH; Target Dataset = output__ATTACH.

【创建及修改时间】
Created: 5/18/2012

Last Modified: 8/19/2012
【原文链接】
http://support.esri.com/en/kno ... 40289