Content deleted Content added
Fabrictramp (talk | contribs) removed deadend tag |
|||
Line 1:
{{internallinks|date=August 2008}}
{{refimprove|date=August 2008}}
Line 10 ⟶ 9:
==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.
; Dexterity Forms:
: Using VBA to handle all the business logic - you can use Dexterity as a new forms creator/editor. This requires the purchase of VBA/Modifier and Customization Site Enabler from MBS.
; 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.
| |||