Yes, ArcCatalog creates a standard Access database table, but enforces the creation of a unique index called OBJECTID (which is not, however, actually a primary key). So what Regina describes should work.
There's an ogr2ogr cheatsheet at BostonGIS (http://www.bostongis.com/?content_name=ogr_cheatsheet). I'm not sure about the relationship classes question, although my suspicion is that the conversion works table-by-table on data (spatial and non-spatial) only. Since the relationship classes are not stored in the feature class or non-spatial table itself (they are stored in a table called GDB_RelClasses), I suspect that ogr2ogr will not do anything to convert them. Can someone confirm? -- Lee Hachadoorian PhD Student, Geography Program in Earth & Environmental Sciences CUNY Graduate Center _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
