New answers tagged

2

To answer your question, the way it works is that the database will return one row for each of the distinct values, but there is no guarantee that every time you use the layer the same rows are returned. What row it latches onto is somewhat arbitrary, especially if people are editing the table in question. Alternatives to the unique identifier that is not ...


5

I think you're misunderstanding the purpose of the unique identifier field, and using in ways that will generate undefined results. When a Query Layer is defined, you are given a great deal of leeway to generate an SQL query. ArcGIS uses that query, with various constraints, to access the data. The most common constraint is a spatial filter clause (using ...


3

First, I hope I understand your setup correctly: You have several tables in SQL, some with tabular data and one table containing Lat/Long columns (probably floating/double precision data type). You would like to join several data tables together and see the information as points in ArcGIS. Possible solution: You should make your join/view directly in ...



Top 50 recent answers are included