Skip to content

Verify Table Prefix Order

Roberto Artigas edited this page Aug 7, 2025 · 15 revisions

Please note that this template is the only one currently that will show you the ALIAS in your dictionary. The prefix has to be unique. This is where some discipline and internal standards for your dictionary makes a big difference.

A

A

A

The RED block is the table information. This is the 2nd administrative division, defined as county in the US.

The PURPLE block are fields necessary for NetTalk synchronization. Pay attention to the field options mentioned in the NetTalk documentation.

The GREEN block are the indexes necessary for NetTalk synchronization mentioned in the NetTalk documentation.

The YELLOW block is the alias information.

A

The system defaults file give basic information about internationalization. The country information about international language, calendar, time zones, administrative divisions, continents, currency, and the different names for the components for internationalization.

The RED block contains the field names.

The PURPLE block contains the field external names related to NetTalk synchronization. Check out the NetTalk documentation.

The GREEN block shows the initialization parameters for all the fields.

The YELLOW block shows the field option to make it easier to track the fields that are GUID's in this table.

A

The RED block contains the field names.

The PURPLE block is an alias definition for this table.

The GREEN block shows the initialization parameters for all the fields.

The YELLOW block shows the field option to make it easier to track the fields that are GUID's in this table.

A

The RED block is the table information. This is the unit-of-measure table. Please note the prefix for this table is U004.

The PURPLE block contains the external name for keys for this table. There are naming conventions for external keys. And if you look at the broken arrow you see that the middle component for the external key is the prefix. This guarantees unique key names for your SQL back engine.

The GREEN block shows the key field list. Please note that these have an asterisk at the end of the list. This is an indicator that the field list is bigger than it will fit on the allotted space, and it has been truncated.

The YELLOW block is the aliases for the unit-of measure table.

A

A

This is the geographic boundary table. Used to correlate GIS data to an SQL row record. The actual GIS latitude, longitude, altitude, and type of feature are kept in another geographical based table.

The RED block is the table and alias information.

The PURPLE block points to the GUID and GUID_Parent. GIS entries tend to be hierarchical entries and if you look at options you might notice the Ultra Tree options for the dealing with those type of relationships/

The GREEN block contains references to other data sources for GIS data.

The YELLOW block contains the references from the GIS entries to the different geographic boundary table entries.

A

This is a sample software system users table.

The RED block points to the table and alias definitions.

The PURPLE block points to the different named components for the NetTalk synchronization process.

The GREEN block shows some procedures you might need to define to provide data defaults.

The YELLOW block points to some indexes that are not used on the SQL backend so the options say not to generate these items.

A

The conversion of units-of-measure table entries requires some interesting entries.

The RED block points to the table and alias definitions.

The PURPLE block contains the GUIDs for both the FROM and the TO components of the conversion.

The GREEN block contains the values associated with the conversion from one value to another.

The YELLOW block shows that the key field list is being trucated.

A

No checkboxes on, gets you a table list with aliases.

A

A A

Code Wiki Main Repositories

The way to create something great is to create something simple... progress requires simplicity; and simplicity requires ruthlessness. This helps to explain why simple is as rare as it is beautiful.
- Richard Koch

Clone this wiki locally