The default folder for the Enviro Data files is C:\Enviro\Edata8. There are desktop icons to run the programs: EDITOR, and VIEWER.
The Enviro Data system consists of many program and data files. These are Access format databases that contain user settings, program file, a blank databases for creating subsets, export files, or saved validation data files.There are also Excel files used a examples for the Tour and training.
The main Access files include:
EnvDAdmin.mdb: This is the EDITOR program for building databases. Data administrators can use the program to import, edit, and review data.
EnvDView.mdb: This is the VIEWER program for selecting and retrieving data.
EnvDData8.mdb: This is a sample database provided by Geotech for users and administrators to learn and practice with.
Settings8.mdb: This file remembers the last database attachment and other control information, and stores saved queries by user. These are separated from the program file so that they are not overwritten during installation of program upgrades.
BlankDB8.mdb: This file is an empty copy of the database. The program uses this file to place data selected by you into a subset database, to create a new database with the lookup tables populated, or to create a reference file to send to your laboratory.
DataDB.mdb: This file contains an empty ValidationImport table used for saving validation data sets.
ExportDB.mdb: This file is an empty database used by the Access One Line Table export.
Controls8.mdb: This file contains copies of tables from the Settings file for use during program upgrades.
Xtab_Template.xlsm – This file is the template used to create the crosstab export in Excel. You should not modify without speaking to Geotech support.
System administrators create ODBC (client-server) databases, which can be company-wide or project specific. The database contains tables and relationships in the format described in Appendix A, Data Model of the documentation.
Access database file locations are dependent on the computer type, maintenance requirements, and local area network setups/performance issues. Each user requires his or her own copy of the Access program and support files, including EnvDAdmin.mdb, EnvDView.mdb, Settings8.mdb, BlankDB8.mdb, DataDB.mdb, and ExportDB.mdb, to run the program and save individual user settings. However, network design and resulting performance of the program may require that files be loaded locally, with a corresponding increase in maintenance time requirements, but possibly quicker operation. It is NOT recommended to have a single shared copy of the program files on a network drive, and have multiple users share that set of program files. This will certainly lead to poor performance and may lead to data corruption.
The database files used to store your data (as opposed to program files) can be located on a local or network machine, depending on database type. An Access data file can be located on an individual machine or on a server for multi-user access. To use a SQL Server or Oracle database, an ODBC data source must be created on the client computer for each database to be used by that client. An ODBC database is usually located on a server. ODBC databases are often located in, and managed by, your Information Technology or similar department.