Database objects
Database objects are one level up from Query objects in the object hierarchy. Database objects have three main functions:
To access a database
Database-level security
Database-level methods
Accessing a database
A Database object is needed to access SQL databases, ODBC databases, and any other tables you are accessing through a BDE alias.
Before you can use a Database object, you must set up BDE to access the database by using the BDE Administrator (available from the dBASE Plus program group).
To connect a Database object to a database, set the Database object’s databaseName property to the BDE alias for the database.
Database-level security
Many SQL and ODBC databases require the user to log in to the database. You can preset the Database object’s loginString property with a valid user name and password to log in to the database automatically.
Because each Database object represents access to a database, you can have multiple Database objects that are logged in as different users to the same database.
Database-level methods
The Database object contains methods to perform database-level operations such as transaction logging and rollback, table copying, and re-indexing. Different database formats support each method to varying degrees. Before accessing the methods of a Database object, the Database object itself must be active. The methods of a Database object will not function properly when it's active property is set to "false".
Default Database object
To provide direct, built-in access to the BDE-standard table types (dBASE and Paradox), each session includes a default Database object that does not have a BDE alias. When you create a Query object, it is initially assigned to the default Database object. Thus, if you’re accessing dBASE or Paradox tables without an alias, you don’t need to use a Database object.
If you’re accessing other table types, you need to use the Database object.