Microsoft Dexterity Programming Challenges – Alba Spectrum Texas - Former Great Plains Software Dexterity was designed as a core of Great Plains Dynamics: programming shell, DB independence layer, Integrated Development Environment (EDI) – however this design was performed back in earlier 1990th, so you may imagine that software customization, development and programming goals, pitfalls and priorities shifted. In this small article we will try to orient you in how you should consider your current Microsoft Dexterity modification upgrade, what are dex pluses and minuses from contemporary programmer standpoint: • OOP or object oriented programming. If you look back to programming concept developing in 1980th and earlier 1990th – you will find that those days procedural programming as prevailing and object oriented programming was already invented but not yet implemented into “mass production”. Dexterity is rather procedural scripting language, which was written in C programming language in its turn. Later on in late 1990th GPS tried to switch dex to OOP, when Great Plains decided to develop from scratch its own Purchase Order module (and not to purchase and incorporate Intellisol Advanced Purchase Order Processing/Project Accounting), however it was rather too complicated and later on the idea lost its support • Dexterity vs eConnect programming balancing.