RAD Studio (Common)

These dialogs are used to interact with databases in RAD Studio.

Use this dialog box to create a persistent field component for a dataset.
Each time you open the dataset, the product verifies that each non-calculated persistent field exists or can be created from data in the database, and then creates persistent components for the fields you specified. If it cannot, it raises an exception warning you that the field is not valid, and does not open the dataset.
After you have created a field component for the dataset, the product no longer creates dynamic field components for every column in the underlying database.
Tip: To select multiple fields, press CTRL... more 
Use this dialog box to copy the current set of records from another dataset to the selected client dataset. This is useful when populating client datasets for use as lookup tables, or when testing client datasets at design-time. Select the dataset you want to copy from the list of datasets available to the current form, then click OK. To clear the records in a client dataset at design-time, set the dataset's Active property to true, then right-click the client dataset and choose Clear Data. 
Use this dialog box to construct the command text (SQL statement) for dataset components that have a CommandText property. The dialog buttons add SELECT and FROM clauses; other clauses (WHERE, GROUP BY, HAVING, ORDER BY, and so on) must be added manually to the SQL edit control.  
Use this dialog box to specify the connection string used to connect an ADO data component to an ADO data store. You can type the connection string, build it using an ADO-supplied dialog box, or place the string in a file.  
Use this dialog box to set up the connection to a database.  
Use this dialog to examine the tables, columns, and other properties of a dataset.
The left pane of the dialog displays the dataset and its tables. Select an object in the left pane to display its properties in a read-only grid in the right pane. 
Use this dialog box to see what files are associated with each dbExpress driver name. These associations are stored in the drivers.ini file.  
Use this dialog box to establish a master-detail relationship between two tables.  
Use this dialog box to add new persistent fields to a dataset and create data fields, calculated fields, and lookup fields. The dialog box is displayed when you right-click any of several dataset components, such as TClientDataSet, and choose Fields Editor.
Use the Fields Editor at design time to create persistent lists of the field components used by the datasets in your application. Persistent fields component lists are stored in your application, and do not change even if the structure of a database underlying a dataset is changed. All fields in a dataset are either persistent or dynamic. 
Use this dialog box to define a foreign key constraint between tables in a dataset. The table you selected when navigating to this dialog is automatically set to the foreign key table. You could, therefore, attempt to set the master table in a master-detail relationship to be the detail table. This could, at the very least return unpredictable results. If the actual detail, or foreign key, table's foreign key column contains duplicates, you may generate a design-time error.  
Use this dialog box to create a new named database connection configuration.  
Use this dialog box to create persistent fields in a dataset. You can add persistent fields or replace existing persistent fields.  
Enter a new name for the currently selected named connection in the Connection Builder. Renaming a connection updates the dbxconnections.ini file to change the name for the selected connection configuration. The old name becomes unavailable and can no longer be used as the ConnectionName property of a TSQLConnection component. 
DatabaseSQL Monitor
Use this dialog box to see the actual statement calls made through SQL Links to a remote server or through the ODBC socket to an ODBC data source.
You can monitor different types of activity by choosing OptionsTrace Options to display the Trace Options dialog box. 
Use this dialog box to specify the fields used to sort records in a SQL dataset, which has the CommandType property set to ctTable.  
The Database Editor dialog box sets up the properties of a database that specify the connection that should be made to a database. This dialog box allows you to specify the type of database, the connection parameters, the user name, SQL role, and password, and whether or not a login prompt is required.
These properties of the database component, as well as others, can also be specified using the Object Inspector.
To display the Database Editor dialog box, double click on an IBDatabase component. 
The Transaction Editor dialog box allows you to set up transaction parameters. This dialog box gives you four default transaction settings, which you can then customize if you wish. Once you modify the default transaction, the radio button is unset.
For a complete list of all the InterBase transaction parameters, refer to 'Working with Transactions' in the InterBase API Guide.
These properties of the transaction component, as well as others, can also be specified using the Object inspector.
To display the Transaction Editor dialog box, double click on an IBTransaction component. The following four choices are displayed: 
Use the editor to create SQL statements for updating a dataset.
The TIBUpdateSQL object must be associated with a TIBQuery object by setting the TIBQuery property UpdateObject to the name of the TIBUpdateSQL object used to contain the SQL statements. A datasource and database name must be selected for the TIBQuery object. In addition, the SQL property must include an SQL statement defining a table.
To open the SQL editor:
  1. Select the TIBUpdateSQL or TIBDataSet object in the form.
  2. Right-click and choose Update SQL editor or DataSet editor.
The Update SQL editor has two pages, the Options page and the... more 
Copyright(C) 2009 Embarcadero Technologies, Inc. All Rights Reserved.
What do you think about this topic? Send feedback!