Make Query Table problem

4582
14
10-22-2015 09:11 AM
AndreasStelter
New Contributor

Hi,

I am trying to join three tables from the same FGDB via Make Query table.

Validation in Model Builder shows no errors. If I run my tool from Model Builder the following error messages are displayed:

ERROR 999999: Error executing function.

An expected Field was not found or could not be retrieved properly. [S_LX_Abzugsbefreiungen_Query]

An expected Field was not found or could not be retrieved properly. [OID]

Failed to execute (Make Query Table).

What's wrong? S_LX_Abzugsbefreiungen_Query is the name of the table that should be created.

The error persists even if I remove the SQL query, so the reason cannot be a syntax error in th query.

BTW: I'm using ArcGIS 10.0 SP5.

Thanks for any help

Andreas

0 Kudos
14 Replies
AndreasStelter
New Contributor

Same problem in ArcGIS 10.2.2.

0 Kudos
JakeSkinner
Esri Esteemed Contributor

Hi Andreas,

This is a bug:

NIM102585:  In ArcGIS Desktop 10.2.2, the quotes have to be either removed or modified in the Expression column of the Make Query table tool to run the tool successfully.

Remove the quotes around your SQL expression and it should work.  Ex:

Change:

"centroid_1301.BlockLotQ" = "Municipality_1301.BlockLotQ"

to:

centroid_1301.BlockLotQ = Municipality_1301.BlockLotQ

AndreasStelter
New Contributor

Hi Jake,

I already tried that, but it didn't solve my problem.

Andreas

0 Kudos
JakeSkinner
Esri Esteemed Contributor

Can you send a screen shot of how you have the tool setup?

0 Kudos
AndreasStelter
New Contributor

Screen shot:

makequerytable.PNG

0 Kudos
jessemaps
Occasional Contributor

A note on removing the quotes from the field names in the expression...

After removing quotes from field names you will still get the error if you "verify" in the Query Builder, but when you run the tool it will execute successfully despite the warning in Query Builder.

0 Kudos
ShawnCarson
New Contributor III

Thanks for this info Jesse. I just spent 45 minutes trying to avoid the error. 

0 Kudos
DrewDowling
Occasional Contributor III

Still an issue in 10.3.1

0 Kudos
AndreasStelter
New Contributor

I found a solution for my problem without changing the model.

0 Kudos