<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Behavior of Views Created by Create Database View GP Tool in 10.1 in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/behavior-of-views-created-by-create-database-view/m-p/517976#M29372</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I wrote a Python script with ArcGIS 10.1 that runs the "Create Database View" GP tool to make views for all of an ArcSDE geodatabase's featureclasses and non-spatial tables.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The views appear to be created okay (using SELECT * FROM &amp;lt;TABLE&amp;gt;).&amp;nbsp; However....&amp;nbsp;&amp;nbsp; for some of the views, ...only some..., ArcCatalog previews the geography but returns an error message when previewing the table.&amp;nbsp; It returns a vague message (about assuring you have an OID) instead of showing the table.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When any of the views (whether or not the table previews in ArcCatalog) is added to ArcMap, ArcMap treats the view as a Query Layer and prompts for the unique ID field.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Why might only some views of featureclasses not show their tables in ArcCatalog?&amp;nbsp; Am I missing something?&amp;nbsp; Should these views be used as Query Layers?&amp;nbsp; Is there something that I need to do in order to cause the views to behave the same way as their underlying featureclasses?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Jan 2013 23:56:15 GMT</pubDate>
    <dc:creator>IvanBrown</dc:creator>
    <dc:date>2013-01-23T23:56:15Z</dc:date>
    <item>
      <title>Behavior of Views Created by Create Database View GP Tool in 10.1</title>
      <link>https://community.esri.com/t5/data-management-questions/behavior-of-views-created-by-create-database-view/m-p/517976#M29372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I wrote a Python script with ArcGIS 10.1 that runs the "Create Database View" GP tool to make views for all of an ArcSDE geodatabase's featureclasses and non-spatial tables.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The views appear to be created okay (using SELECT * FROM &amp;lt;TABLE&amp;gt;).&amp;nbsp; However....&amp;nbsp;&amp;nbsp; for some of the views, ...only some..., ArcCatalog previews the geography but returns an error message when previewing the table.&amp;nbsp; It returns a vague message (about assuring you have an OID) instead of showing the table.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When any of the views (whether or not the table previews in ArcCatalog) is added to ArcMap, ArcMap treats the view as a Query Layer and prompts for the unique ID field.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Why might only some views of featureclasses not show their tables in ArcCatalog?&amp;nbsp; Am I missing something?&amp;nbsp; Should these views be used as Query Layers?&amp;nbsp; Is there something that I need to do in order to cause the views to behave the same way as their underlying featureclasses?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2013 23:56:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/behavior-of-views-created-by-create-database-view/m-p/517976#M29372</guid>
      <dc:creator>IvanBrown</dc:creator>
      <dc:date>2013-01-23T23:56:15Z</dc:date>
    </item>
  </channel>
</rss>

