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.
The views appear to be created okay (using SELECT * FROM <TABLE>). However.... for some of the views, ...only some..., ArcCatalog previews the geography but returns an error message when previewing the table. It returns a vague message (about assuring you have an OID) instead of showing the table.
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.
Why might only some views of featureclasses not show their tables in ArcCatalog? Am I missing something? Should these views be used as Query Layers? Is there something that I need to do in order to cause the views to behave the same way as their underlying featureclasses?
