ArcView Database Access 2.1b Extension (PC only)
The ArcView Database Access 2.1b extension extends ArcView GIS 3.2 to connect to ArcSDE 8.1 servers.Description
The ArcView Database Access 2.1b extension extends ArcView GIS 3.2 to connect to ArcSDE 8.1 servers. This release also supports ArcGIS 8.1 Direct Connect to Oracle 8i and SQLServer. There have been no changes to the functionality since Database Access 2.0 was released with ArcView GIS 3.2
Note: See the Database Access readme file for more information about ArcView Database Access 2.1b for ArcView 3.2.
When you retrieve data from a database, you can now see it in a database table. Database tables share the existing Table user interface but do not support all of the functions provided such as indexing. A copy of your data is not written locally the way it is now using the SQL Connect functionality. You will only be able to see a portion of the retrieved data in one database table at a time, but you can increase the number of records displayed in the table as is appropriate. You will be able to create database tables from database themes clicking the Open Theme Table button.
Database Themes Display Query Results
When you query a database you retrieve a set of fields and records. A database theme represents the set of records and displays the spatial data contained by one of the fields. The data retrieved can be the product of joining several tables in the database together. Creating a database theme is similar to creating an SQL SELECT statement. When creating a database theme from an SDE database you can now specify spatial constraints in addition to attribute constraints.
Accessing Data from Many Databases at the Same Time
You can now connect to many SDE databases at the same time. This means you can have several database themes visible in a view whose source data is located in different SDE databases. If you have an SDE connection to a database, you can handle nonspatial data using the same connection. You do not need to create an additional ODBC connection to the database to work with nonspatial tables.
Spatial Data Is Integrated with Attribute Data
In an SDE database, any table can be turned into a spatial table by adding a spatial column to it. Spatial data can now be truly integrated in your database design.
Area of Interest Support
Since you can apply spatial constraints to database themes, we are providing Area of Interest support through Avenue requests only. Using the current functionality, when you set an Area of Interest the same restraints are applied to all the themes in a view. This functionality is too limiting for database themes, which do not have tiles and which support theme-based Areas of Interest. Using Avenue you can apply different spatial constraints to each theme in the view and multiple spatial constraints to one theme. The spatial constraints are not limited to rectangles, either; for example, you could create a spatial filter using a buffer generated around the selected features in a theme.Supporting Files :