A “true” key in an ISAM data file. See foreign key.
A number from 0 to 255 that determines who can access a table and how. Each table has an access level, as does each group. A user may view only those tables whose access level is equal to or lower than access level of the group to which the user belongs. Additionally, access levels determine whether data can be modified.
Characteristics of a repository structure that describe fields, keys, relations, tags, and redisplay formats.
Used interchangeably with field. For the purposes of xfODBC, a system catalog column is equivalent to a repository field.
A text file containing datasource (data file location) and dictsource (system catalog path) definitions. This file is used by DBA when opening a system catalog and xfODBC when accessing a Synergy database.
conversion setup file
A text file containing table access levels and data file location, generated by DBA.
A set of classes that provide ADO.NET access to a data source, as well as data services. For example, the .NET Framework includes the .NET Framework Data Provider for ODBC, which provides ADO.NET access to ODBC data sources.
A set of related files created and managed by a database management system (DBMS). Database and file structures are determined by the software application in which it is generated. Although the term database is sometimes used to refer to the combination of a software application and a data source, this manual considers data source and database to be analogous.
Database Administrator (DBA)
An xfODBC component that enables you to generate, maintain, customize, and verify the system catalog; create user access; and generate a conversion setup file.
The xfODBC utility used to generate a system catalog and initialize user and group access.
A text file you write to define the data environment variables that are used by xfODBC when locating Synergy data files. The environment setup file is typically used for setting environment variables that are used in the Open filename field of a repository file definition.
A record component that contains an individual data element. Used interchangeably with column. For the purposes of xfODBC, a repository field is equivalent to a system catalog column.
A key used to specify relationships between files but which is not a true key in the data file. (Foreign keys are defined in the repository.)
One or more users with the same database access level defined in the group catalog.
A structure within a structure, as defined by the Synergy DBL GROUP statement. Fields or other group definitions can be members of a group.
The SODBC_GROUPS.* files that contain group ID, group name, and user access information.
A common method for keeping track of information in a Synergy Database file or a database by storing key information. See key.
Indexed Sequential Access Method. A file access method that stores data sequentially while maintaining an index of key fields.
A value or field used to identify and locate records in a data file and to define a sequential order in which to process that file. For practical purposes, key and index are used interchangeably.
key of reference
A key that defines which ISAM file index is used in sequential operations.
A specific, constant value, as opposed to a variable. Both numbers and text can be literal values.
.NET Framework Data Provider for ODBC
An ADO.NET data provider included with the .NET Framework that enables access from .NET applications to ODBC data sources.
Open Database Connectivity. A standard API for accessing databases in a Windows environment.
ODBC Driver Manager
A dynamic‑link library (DLL) provided by Microsoft. The Driver Manager opens and closes ODBC drivers as directed by an ODBC‑enabled application.
A front‑end or client application running on Windows that uses an ODBC API to access various types of databases.
A data area containing one or more consecutive fields on a related subject, such as a customer record or a file layout.
An attribute of structures that enables you to link the keys of one structure with the keys of other structures.
A file that consists of a series of fixed‑length records referenced by relative position in the file.
The files generated by S/DE Repository. These files describe your actual data files.
A Synergy application used to define files, structures, tags, fields, and keys for a database; dbcreate translates these repository definitions into system catalogs.
See Synergy Runtime.
A column that is a part or section of an index or key.
An ADO.NET term for an object that implements the IEnumerable or IQueryable interface.
A record definition or the collection of field and key characteristics for a particular file or files.
A database comprising data files and repository files; the two sets of files together constitute a Synergy database.
The Synergy component required for Synergy applications, such as DBA, to run.
A set of files generated by dbcreate and consisting of the individual table, user, group, column, index, segment, tag, and relation catalogs. The system catalog contains a “translation” of the Synergy database in a form that ODBC‑enabled applications can understand.
Used to refer to the level at which some environment variables must be set. A system‑wide environment variable is available to all applications running on the system.
The GENESIS_TABLES.* files that contain file and structure information as well as data table access information.
A set of characters, usually a field or part of a field, that is used for identifying or grouping records in a data structure.
The sodbc_users.* files that contain user name, password, and group ID information.
A routine that enables you to customize and generalize the data filenames specified in a system catalog.
A package of components that enables you to make your Synergy data accessible to third‑party applications. xfODBC includes the xfODBC driver and two utilities, the xfODBC Database Administrator (DBA) program and dbcreate, used to create system catalogs from your Synergy repository definitions.