Content deleted Content added
Grammatical and accuracy |
TimGordon81 (talk | contribs) m grammar |
||
Line 2:
The '''Dexterity programming language''' was designed in the early 1990s for the implementation of [[Cross-platform|platform independent]] graphical [[accounting software]]. Dexterity itself is written in the [[C (programming language)|C programming language]] [http://www.devnewz.com/devnewz-3-20040827GreatPlainsDexterityProgrammingOverviewforDevelopers.html]. It was used in the development of [[Great Plains (accounting)|Great Plains]] accounting software.
[[Microsoft Dynamics|Microsoft Business Solutions]] GP, formerly Great Plains Dynamics and eEnterprise, is a Dexterity-written
==History of Dexterity==
Line 13:
:Currently, most Dynamics GP installations have been moved to [[Microsoft SQL Server|MS SQL]] Server - so you can use Dexterity for custom forms drawing only and make the buttons run SQL stored procedures.
; COM Object calls:
: Beginning with version 7.0, Dexterity supports COM objects - register them as libraries in Dexterity. Refer to the manual as to how to do this. This technique allows you to call such things as [[web service]]s across the internet.
; Dynamics GP Alternate Forms:
: These are modifications to existing forms – the ones found in DYNAMICS.DIC. The most popular customizations are made on the SOP Entry form. Alternate forms are not recommended by Microsoft as they
; Some restrictions:
: Dynamics GP is actually an integration of multiple dictionaries: DYNAMICS.DIC, ADVSECUR.DIC, EXP1493.DIC, etc. In your Dexterity customization you can generally deal with only one dictionary - DYNAMICS.DIC. Integration with other dictionaries is supported but is difficult.
Dynamics GP macros can also be recorded in Dexterity. The ability to handle [[branch (computer science)|branches]] does not appear to exist in these macros.
|