Database Reference
In-Depth Information
•
Items created before UI Defaults have been established don't inherit prop-
erties of the UI Default.
•
Developers can choose not to use UI Defaults, and even if they're used, can
override them after the component is created.
Having said that, UI Defaults do help ensure consistency across your application
and make your job much easier as a developer.
Defining UI Defaults for Tables
UI Defaults can be managed either from SQL Workshop's Object Browser or from
SQL Workshop's Utilities page. Here's what to do:
1.
Navigate to SQL Workshop's UI Defaults page by clicking the arrow on the
SQL Workshop tab and selecting
User Interface Defaults
from the drop-
down menu.
You're taken to the UI Defaults dashboard where things likely look
pretty sparse. This is because you haven't actually created any UI Defaults
yet. The first step to creating UI Defaults is to synchronize the Table Dic-
tionary with the database so it knows what tables are in your schema.
2.
Click the
Manage Table Dictionary
button, and then click the
Synchron-
ize
button on the screen that appears.
This initiates the Synchronization Wizard. This wizard shows you the
number of tables with defaults defined and the number without. In this
case, you should have zero tables with defaults and four tables without.
3.
Click the
Synchronize Defaults
button to begin the synchronization with
the database. This may take a little time.
Once the Table Dictionary is synchronized with the definitions is the
database, you're presented with the report in
Figure 4-25
that shows each
table that now has base UI Defaults. If you have other tables in your
schema, they also appear in this report.
