Make Query Table - Field conversion

[ChrisMatthews]

Hello

I'm creating a model that is sucking in data from an Oracle database, which I intend to turn into an Event Layer.

Usually this is pretty simple, however on this occation the X and Y coordinates have been stored as strings.

Is it possible to convert field data types when bringing in the data with the Make Query Table tool. Clearly if I was using straight SQL to the database I could do that)?


All help and suggestions appreciated.

Regards

Chris

[RichardFairhurst]

From what I understand, the data source is a non-spatial table in an Oracle database.  I am not exactly sure how to use the Feature Class to Feature Class tool in this instance as the source is simply attributes not registerd with any SDE.  Also, from the docs, http://resources.arcgis.com/en/help/main/10.1/index.html#//001200000027000000 the Table to Table conversion input data types does not seem have an Oracle table as an option either.

The OP is going to have to perform some way to connect and query the data source, then create some mechanism that will transform the result to an output format desired or needed (my example shows that it will be saved as a GDB table).

I mentioned both tools because they operate similarly to convert field types, but you are correct that in this case only the Table to Table tool was potentially an option.  Nothing of what you say about the source was explained, so my question was valid given what the user had said.

Anyway if Python does it that is nice, but only about 20 people on this forum could have come up with that solution.  (Okay, I don't know the number of people with this level of skill, but it is very small compared to the overall forum population).  In fact I am one of the people who is capable of it, but I am slow doing it.  In any case, I demand solutions from ESRI that are designed for non-programmers to do a basic operation like data conversion involving a recasting of a field.  Resorting to Python as the only option is unacceptably unfriendly from my perspective.

So long as only skilled programmers can do field conversions like this ESRI has failed its users and should be openly challenged and criticized until they can do a better job of supporting their users.

[JamesCrandall]

Anyway if Python does it that is nice, but only about 20 people on this forum could have come up with that solution.  I demand solutions from ESRI that are designed for non-programmers to do a basic operation like data conversion involving a recasting of a field.  Resorting to Python as the only option is unacceptably unfriendly from my perspective.

Field mapping is always a tough bug 🙂 

In any event, I think your demand is not that...well.... demanding.