Skip navigation
All Places > Esri Technical Support > Blog > 2010 > December
Ah, the holidays. What better time of year for joining together with friends, families…and tables? Hello, this is Cassandra again bringing you the good tidings of tips for making sure your tables join in harmony.

We talk to a many customers who experience odd problems with data that has been joined, such as an attribute table that contains NULL values, empty output or odd errors when performing geoprocessing. The most common reason why these problems occur is because one or more of the field names in the joined table or the name of the joined table itself does not follow the required naming convention rules.

Naming convention rules, as directed by the Microsoft JET engine, which enables Windows applications like ArcMap to read various table formats, include the following:

- The name must start with a letter, not a number.
- The name must not contain spaces.- The only special character allowed is an underscore.

Take a look at this Excel table – how many names do you see that will cause problems?


If you experience problems performing joins or relates or displaying XY data on tables, exporting the resultant joined table or performing subsequent geoprocessing on a joined table, your first step should be to check all the field and table names.

Another trick I’ve learned when your problem is a field name but you don’t see any problems, is to save the table as a CSV format file and then try to add that CSV into ArcMap. If there is a problem with any field name, ArcMap will display an error message stating which field is the problem.


So, while I can’t fix Aunt Harriet’s fruitcake or that crazy tie you got in the Holiday secret Santa exchange, take comfort that you know your tables join.

Happy holidays from all of us at Esri Support Services!


A lot of users often have questions concerning their system configuration for the version of software being used in conjunction with our products. Questions get more specific to involve installing patches, service packs, etc., within an environment and, in relation to ArcSDE Enterprise geodatabases, questions also involve RDBMS patches. Let’s outline some of the key points made in our Supported Environment Policy document that should help you answer these questions when considering patching a test or production database that houses ArcSDE Enterprise geodatabases.

Support Environment Policy

Meet or exceed the minimum requirements:

  • As a rule of thumb, ensure your configuration meets or exceeds the minimum configuration listed on our system requirements page.
  • Non-certification of an environment does not necessarily mean it is not supported.
  • An environment is supported if it meets or exceeds the base build environment and that environment is not known to fail.

Check out the ‘limitations’ section of the system requirements page:

  • Environments that are known to not work are usually documented on the product support page as soon as that information is available.
  • An environment may be supported even if there are some known issues with the software on that particular environment (any known issues will be documented in the "limitations" section of the System Requirements for that environment).

Check that the 3rd-party vendor supports the environment:

  • Esri cannot support any environment not supported by the vendors of the operating systems, RDBMSs, or Web servers.

Test, test, test!
Since Esri cannot test and certify every possible configuration, it is always recommended to thoroughly test any upgrade or change to your production environment on a test server first. This helps to ensure your organization’s workflows prior to implementing such a change.

Geodatabase and ArcSDE System Requirements – Version 10.0

ArcGIS Server 9.3/9.3.1 System Requirements - see Supported Relational Database Management Systems (ArcSDE) section

How many times have you tried to geocode a point somewhere in the continental United States and the point appears off the coast of East Africa? For example, you call Esri Support and we tell you that the locator is giving you lat/long but your map service is using a projection other than WGS 1984, Web Mercator, for instance. Solution? Re-project your geocoded results: from Geographic to Web Mercator. If your map service uses a spatial reference other than Web Mercator, then you would need to use a Geometry Service to do the reprojection.

OutSpatialReference (Silverlight, Flex, JavaScript). This is the keyword that is going to make life easier for you. A new property of the Locator task (or of AddressToLocationsParameters class in Silverlight) introduced in the ArcGIS Server 10.0 REST API and henceforth in the 2.x Web APIs allows you to set the spatial reference of the output geometries.

For example, setting the outSpatialReference in JavaScript API
locator = new esri.tasks.Locator("http://<SERVER>/ArcGIS/rest/services/<LOCATORSERVICE>/GeocodeServer"); locator.outSpatialReference = new esri.SpatialReference(102113);

This property is available only with ArcGIS Server 10.0 and later releases. So, make sure that in your 2.x Web API application, you are working with Locator services hosted on a 10.0 machine.

- Kripa J., Esri Support Analyst - SDK group, Esri Support Services

esri logo

We are pleased to announce to our ArcPad customers that Service Pack 1 for the 10.0 release is now available for download at the Esri Customer Care website:

If you have any questions or run into issues with the installation please contact Esri Technical Support at 1-888-377-4575, option 2, or visit the Support site. Users outside the United States should contact their local distributor for help.


UPDATE: 12/15/10

A version of ArcPad with SP1 included is available for download on the Esri Customer Care website under the "Software Downloads" section.  Authorized contacts that are able to download ArcPad can also get this new version that has Service Pack 1 included.


Mike H., Program Manager
User Advocacy Group, Esri Support Services

Mike H., Program Manager
 Follow me on Twitter:

Greetings! This is Emeline and I'm here to provide some pointers to prepare for using the new ArcGIS Viewer for Flex. The ArcGIS Viewer for Flex offers an easily configurable but super cool application for showing off your ArcIMS and ArcGIS Server map services! Before you add your services to the Flex Viewer application, you’ll need to work through a few initial steps first:esri logo
  1. Make sure your map service is ready to mash up with ArcGIS Online services. In order to use your services in the Flex Viewer, you’ll need to change the map to use the WGS 1984 Web Mercator (Auxiliary Sphere projection).
  2. If you make changes to the map document (step 1 for example), be sure to clear your REST services directory cache.
  3. Be sure to add your services within the <operationallayers> tag, and not the <basemaps> tag (unless you want to use your own basemaps, instead of the ArcGIS Online services).
  4. If you haven’t cached your map services, make sure you change the type property of the <layer> tag to “dynamic” instead of “tiled”.
  5. If your Flex Viewer is hosted on a different server than the ArcGIS or ArcIMS layer you are adding, then the machine with the ArcGIS or ArcIMS needs to have a crossdomain.xml file.

    For a complete introduction to the Flex Viewer, check out the  Introduction to the ArcGIS Viewer for Flex training seminar. I hope you enjoy the Flex Viewer, and be sure to check out the Flex Viewer Blog for the latest tips & tricks!

    Happy Mapping!

    Emeline R.

    ArcGIS Server Senior Support Analyst

    Filter Blog

    By date: By tag: