Framework Code Tables

This documentation is not relevant to VLF-ONE applications.

The Framework Code Tables provide a number of facilities to make it possible to more productively handle codes, decodes and prompting in your application.

Code Tables are: 

Fully configurable

Designers simply specify the keys and data items that define the code table to the Framework.

To design a Currencies code table the Framework designer needs to define the Currency Code as a key and the Currency Description as a Data item.  

May be sourced from your database tables 

The data inside code tables can come from your existing database tables or the Framework can store it automatically.

The Currencies code table could be stored and managed by the Framework itself in its own database table or sourced from one of your own database tables (or from anywhere else that your computer can access).

The format of the code table you define does not have to be the format of the database table it is sourced from. Sometimes the data in a table is sourced from "hard coded" program values. For example the Sex table mentioned previously may be defined as data within a program only and never be actually stored anywhere.   

Can be updated in deployed applications by end-users

Optionally end-user administrators can be allowed to update information stored in code tables.

The user interface for updating the Code Table is provided by the Framework. The final updating and storage of the information in the table can be done automatically by the Framework or by a program that you provide.

Can be visualized by you to your end-users in various ways

Codes can be visualized to end-users in different ways, ranging from a group of radio buttons (e.g. the Sex code table) to a drop-down combo box (e.g. the Currencies code table).    

Are an alternative to defining simple small database tables

Code tables are a way of defining simple tables quickly and easily. They are suited to tables with less than 100 data items, with small numbers of columns (2 - 6), that do not require validation checks when the table data is entered, virtual columns, or indexes.  

If you require functionality beyond these limits, you should define your database table as LANSA tables, and write your own prompt assistant program.