Latest Contributions by MichaelTodd

‎08-29-2023

Of course I posted in the wrong area. Thanks for your useful guiding hint. https://community.esri.com/t5/arcgis-pro-ideas/joining-tables-with-incompatible-column-types/idi-p/1323416

‎08-29-2023

If a user tries to join two tables and the joining columns are incompatible the join will fail, even if there would be a valid match if the columns were the same type. Allowing the join even though it will result in 0 matches can be confusing to a user, especially one who is unfamiliar with how things work at the database level. Instead, a warning or error should appear in the Join window letting the user know that they are about to waste their time, both during the join as well as the hours of frustration afterward trying to figure out why it's not working when it looks like it should. A user spent several days trying to troubleshoot this same issue. He received the warning that the join had no matches when he tried to validate it but did not know enough to recognize what the message meant, i.e. that there was underlying column incompatibility. To the user, 12345 was equal to “12345”. Even something as simple as a message above or below the Join has no matches warning like “cannot join integer and string columns” might have saved the user numerous hours extracting data, deleting columns, and whatever else they did to fix a problem for which they had no useful guiding hints.

‎08-28-2023

This is actually on behalf of a user who spent several days trying to troubleshoot this same issue. He received the warning you displayed but did not know enough to recognize what specifically it meant, I.e. that there was underlying column incompatibility. To the user, 12345 was equal to “12345”. Even something as simple as a message above or below the Join has no matches warning like “cannot join integer and string columns” might have saved the user numerous hours extracting data, deleting columns, and whatever else they did to fix a problem for which they had no useful guiding hints.

‎08-28-2023

If a user tries to join two tables and the joining columns are incompatible the join will fail, even if there would be a valid match if the columns were the same type. Allowing the join even though it will result in 0 matches can be confusing to a user, especially one who is unfamiliar with how things work at the database level. Instead, a warning or error should appear in the Join window letting the user know that they are about to waste their time, both during the join as well as the hours of frustration afterward trying to figure out why it's not working when it looks like it should.

‎11-16-2012

I had this same issue and was able to resolve it by: 1. Uninstalling the web adapter 2. Repairing the ArcGIS Server installation 3. Installing ArcGIS Server SP1 again (seems redundant, but setup didn't complain) 4. Installing the web adapter After doing the above steps I was able to register my server with the web adapter at the end of the web adapter installation.

‎09-04-2012

It turned out that we needed to install the SQL Server Native Client so that our application could communicate with SDE 10.1 via a direct connection. Since we are using SQL Server 2012, we downloaded the native client from the SQL Server 2012 Feature pack located here https://www.microsoft.com/en-us/download/details.aspx?id=29065. Once the native client was installed, the application was able to load layers from SDE 10.1

‎09-04-2012

Unfortunately I'm not connecting to SDE that way (though I may try it if nothing else works). We have always used an MXD to connect to our layers, then loaded the MXD via LoadMxFile into the application. The MXDs I am using works correctly when connecting to SDE 10.0 but do not work when connecting to SDE 10.1 when using our application. However, both MXDs work in ArcMap, so I know there's nothing wrong with the connection per se, just that there's something wrong when I try to connect via ArcGIS Engine. Any other thoughts?

‎08-30-2012

I have an ArcGIS application that works great when loading layers from SDE 10.0 but fails when trying to load the layers when they're pointing to a SDE 10.1 server. The only difference is the layer source in the MXD. When the layer points to the SDE 10.0 server, everything loads as expected. If I change the layer source to point to the exact same layer (name, rows, etc.; it was merely copied over from 10.0 to 10.1) in the SDE 10.1 server, a red exclamation point appears next to the layer name. The SDE 10.1 layers are visible in ArcMap so this shouldn't be a port or instance issue This isn't a licensing issue; I have the app set to exit if the license is invalid/unavailable Is there something special I need to do to get an Engine application to communicate with an SDE 10.1 server? Is this a service file issue? I tried adding a reference to the service name and port for the new server in the services file but it didn't seem to help, but 10.0 and 10.1 seem to do services/instances a little differently; perhaps I'm missing something. UPDATE: The more I think about this, the more it seems to be a "direct connect" issue. Is it possible that I'm not connecting to SDE because things aren't set up right on the client? If so, how do I set up direct connect on an ArcGIS Engine client?

‎08-29-2012

Per ESRI: "It would not be possible to retrieve the same archival information after exporting the feature class into a new geodatabase." So, in other words, one cannot copy archival information from one geodatabase to another. It must always live in the same geodatabase. Once you have transferred a layer to a new geodatabase you can set up versioning and then archiving, but you're essentially creating a _new_ archive that starts from the data that you created it. If you need to retain archival information when moving to a new ArcGIS version and a new server, the recommended course of action is to: 1. Upgrade the geodatabase to the new version 2. Backup the database 3. Restore the database on the new server That should ensure that everything is retained during the move.

‎08-27-2012

I am trying to copy a layer from a server running SDE 10.0 (on SQL Server 2005) to a server running SDE 10.1 (on SQL Server 2012). The layer has versioning and archiving enabled and there does not seem to be a way to copy the archival information. Is there a way to copy the layer and all archiving information as well?

Online Status	Offline
Date Last Visited	‎02-22-2024 09:57 AM

My Ideas

Latest Contributions by MichaelTodd

Re: JOINing tables with incompatible column types should display a warning/error

JOINing tables with incompatible column types should display a warning/error

Re: JOINing tables with incompatible column types should display a warning/error

JOINing tables with incompatible column types should display a warning/error

Re: Server 10.1 SP1 Web Adaptor Error

Re: Engine Application Not Loading Layers from SDE 10.1 Server

Re: Engine Application Not Loading Layers from SDE 10.1 Server

Engine Application Not Loading Layers from SDE 10.1 Server

Re: Copying Archived Layers from One Server to Another

Copying Archived Layers from One Server to Another

JOINing tables with incompatible column types shou...

Re: JOINing tables with incompatible column types ...

JOINing tables with incompatible column types shou...

Re: Copying Archived Layers from One Server to Ano...