Dexterity (programming language)

The Dexterity programming language was designed in the early 1990s for the implementation of platform independent graphical accounting software. Dexterity itself is written in the C programming language [1]. It was used in the development of Great Plains accounting software.

Microsoft Business Solutions Great Plains, former Great Plains Software Dynamics and eEnterprise are Dexterity-written applications. Also small business line: Microsoft Small Business Manager or Small Business Financials is written in Dexterity and uses the same code base as Great Plains.

History of Dexterity

Great Plains Dexterity - is proprietary programming language and technology, designed in the early 1990s with the goal to build a platform-independent graphical accounting package - Great Plains Dynamics. Dexterity itself is written in C (with the hope that C would provide platform independence). You can install Dexterity from Great Plains 7.5 CD #2. It requires a lot of learning and training, but it allows custom pieces to be seamlessly integrated with the Great Plains interface.

Features

Native Dexterity Cursors

Dexterity was designed as a platform-independent programming language. If you want code to be operable on all currently supported Great Plains databases, use Dexterity ranges and loops to manipulate the records

Great Plains Dexterity with SQL Stored Procs

Currently, most of Great Plains installations have been moved to MS SQL Server - so you can use Dexterity for custom forms drawing only and make the buttons run SQL stored procedures.

COM Objects calls

Beginning with version 7.0 Dexterity supports COM objects - register them as libraries in Dexterity. Refer the manual as to how to do this. This technique allows you to call such things as web services across the internet.

Great Plains Alternate Forms

These are modification to existing forms – the ones found in DYNAMICS.DIC. The most popular customizations are made on the SOP Entry form. If you are designing your customization – we recommend that you avoid alternate forms – the problem is customization version upgrade. In the case of an alternate form – customization should be redone.

Some restrictions

Great Plains is actually an integration of multiple dictionaries: DYNAMICS.DIC, ADVSECUR.DIC, EXP1493.DIC, etc. In your Dexterity customization you can deal with one dictionary - DYNAMICS.DIC. If you need cross dictionaries customization - consider using SQL Stored Procs for crossing dictionary borders and pulling data/making changes in the other dictionary.

Great Plains macros are also recorded in Dexterity. The ability to handle branches does not appear to exist in these macros.