Community

All Communities

Products

ArcGIS Survey123 ArcGIS Pro ArcGIS Online ArcGIS Enterprise Data Management ArcGIS Web AppBuilder Geoprocessing ArcGIS Collector ArcGIS Spatial Analyst Imagery and Remote Sensing ArcGIS CityEngine ArcGIS Dashboards All Products Communities

Industries

Education Water Resources Gas and Pipeline State & Local Government Transportation Water Utilities Telecommunications Roads and Highways Natural Resources Electric Science Commercial All Industries Communities

Developers

Python ArcGIS API for JavaScript ArcGIS Runtime SDKs ArcObjects SDK ArcGIS API for Python ArcGIS Pro SDK Developers - General ArcGIS API for Silverlight (Retired) ArcGIS API for Flex (Retired) ArcGIS REST API ArcGIS for Windows Mobile (Retired) File Geodatabase API All Developers Communities

Worldwide

Comunidad Esri Colombia - Ecuador - Panamá ArcGIS 開発者コミュニティ ArcNesia Esri India GeoDev Germany ArcGIS Content - Esri Nederland Esri Italia Community Czech GIS GeoDev Switzerland Swiss Geo Community Comunidad GEOTEC Esri Ireland All Worldwide Communities

All Communities

Products Developers User Groups Industries Services Community Basics Worldwide Events ArcGIS Topics Learning Networks View All Communities
ArcGIS Ideas
Community Basics

Community Help Documents

Community Blog

Community Feedback

Member Introductions

New Contributor

since

‎11-11-2020

1 Posts created

1 Kudos given

0 Solutions

0 Kudos received

My Ideas

(0 Idea Submissions)

Show:

Latest Contributions by TimothySmothers

POST

What exactly does this import wizard do? Could it be clobbering things? I think the suggestion above is a good one; just build a locator with 10.2 that point to your 9.3 SDE feature class. My only additional suggestion is to not include the locator(s) as database objects but rather store them in their stand alone directory.

0

0

10