This is an ArcInfo Workstation issue. It should not occur in ArcGIS.
Not applicable.
Feedback on this topic?
flist