Difference between revisions of "Category:Grids"

Revision as of 07:47, 15 April 2024

Under Construction

Overview

Split Grid

Data Summaries

Searching Data

Querying Data

Sorting Data

Dynamic Badges

Dynamic Spark Line Charts

Dynamic Spark Bar Charts

Dynamic Ratings

StringList Editor

Data Mapping

Business Rules

A business rule is a statement that imposes some form of constraint on a specific aspect of the database, such as the elements within a field specification for a particular field or the characteristics of a given relationship.

Business rules are defined using the Table Designer or in code using the alter table command.

There are a wide range of business rules which can be associated with tables and their columns. These business rules are active whenever a table is opened or bound to a UI element in Desktop, Web, Mobile or ODBC connections that use Lianja SQL Server.

These business rules are contained within the Active Data Dictionary for a table. Changes to these business rules do not require any changes to applications. When the applications are opened and the UI loaded with bound data, by default the business rules are inherited from the Active Data Dictionary.

You can restrict what data is entered by a user using validation, input masks, choicelists and much more.

MetaData

When you associate metadata with tables or columns, you typically define UI attribute names and values. Wherever the table or column is used in any App when the table is opened, the metadata is read and the attributes are then applied to the UI element.

Changes to the metadata are automatically applied across all Apps. No code changes are required.

This provides a powerful means of data binding with associated business logic all without coding. You define metadata for databases, tables, and columns using the MetaData Editor which is integrated into the Table Designer.

Desktop Browse

The browse command is a favorite with Visual FoxPro developers for building desktop applications.

LianjaScript has an enhanced version of browse with split grid editing and many of the features described in above. With business rules defined in the data dictionary for a table and its columns, browse can be used in desktop applications without compromising data integrity.

Example usage:

browse table southwind!employees splitbar title "Employees" ;
properties "showsplitedit=true;splitmemolist=notes;splitimagelist=photo"

Embedding Desktop Browse in a Custom Section

In desktop Apps you can embed a browse command in a custom section.

Add a custom section to a page then in the custom BROWSE command attribute type:

browse table southwind!employees title "Employees"