The first step in configuring
DADE for your end users involves setting the properties of the
DataSettings object of the
Designer component.
This object contains the following properties:
| Property |
Description |
|
AllowEditSQL |
Determines whether or not the end-user
can edit the SQL in the Query Designer. |
|
DatabaseName |
The name of the database from which
data will be retrieved when the query executes. |
|
DataDictionary |
The data dictionary object that will
convert raw table and field names to aliases. |
|
SessionType |
Defaults to BDESession. Should only be
changed if you have created your own Session class in order to use the Query
Wizard with a proprietary database engine. |
|
SQLType |
Defaults to sqBDELocal. If you are not
using dBase or Paradox tables, then you should set this property to sqSQL1,
as the Local SQL dialect is not supported by most other database types. If
your database supports ANSI-92 SQL, then you can set this property to sqSQL2
instead of sqSQL1. |
|
UseDataDictionary |
Determines whether the data dictionary
object assigned to the DataDictionary property will be used. |
If you intend to use the Query Wizard and Query Designer, then the
SQLType is vital. The following table shows
the recommended SQLType for a given database
product.
| Database Product |
SQLType |
|
Paradox |
sqBDELocal |
|
Interbase |
SQL2 |
|
Oracle |
SQL1 |
|
MS Access |
SQL2 |
|
Sybase SQL
Server |
SQL1 |
|
Sybase SQL
Anywhere |
SQL2 |
|
MS SQL Server |
SQL1 |
Once you have configured the data settings, you may notice that
a Data Settings menu option appears on the
File menu of the data workspace when y
ou
run your application. This option displays a
dialog that allows the end-user to modify
the data settings (pictured below). If you
do not want the end-user to be able to
change these settings, then you can set the
AllowDataSettingsChange property of the Designer component
to False.
