Book Image

Developing Microsoft Dynamics GP Business Applications

By : Leslie Vail
Book Image

Developing Microsoft Dynamics GP Business Applications

By: Leslie Vail

Overview of this book

Microsoft Dynamics GP is a sophisticated Enterprise Resource Planning (ERP) application with a multitude of features and options. Microsoft Dynamics GP can also be used to develop dynamic, mission critical applications. In "Developing Microsoft Dynamics GP Business Applications" you will learn how to create and customize Dynamics GP Applications. This hands-on guide will take you through the initial steps of setting up a development environment through to customizing and developing an example application using tools such as Dexterity, VSTools and sanScript. "Developing Microsoft Dynamics GP Business Applications" will take you through the complex steps of creating and customizing Microsoft Dynamics GP applications. Starting with an overview of Microsoft Dynamics GP architecture you'll then move onto setting up your development environment. You will learn how to make your application come to life with Dexterity and sanScript. You will create table operations and ranges as well as object triggers to make powerful and practical business applications. You will deploy your Dexterity solution before moving onto customization with Modifier and VBA. This book will also take you through ways of enhancing and extending your application without code using the SmartList Builder and Excel Report Builder. Using these highly flexible tools you'll be able to create data connections that will increase the usability and functionality of your ERP applications.
Table of Contents (15 chapters)
Developing Microsoft Dynamics GP Business Applications
Credits
About the Author
Index

Minding versions and builds


When you create your chunk file for deployment, you will be asked to assign it a major version, minor version, and build number. The runtime engine reads the version and build numbers and compares them to any existing dictionary for that product ID. If the version numbers match, the build numbers are examined. If the build number in the chunk is equal to or greater than the build number of the existing dictionary, a new dictionary will be created by your chunk.

If the version numbers do not match, or the build number is lower than the existing dictionary, the file will remain a .cnk file and a message similar to the following message will be written to the installerrors.txt file:

Version 11.0.17 of Contacts.cnk is not compatible with version 11.1.15 of CONTACTS.DIC

This keeps you from accidentally installing an older version of a dictionary. On the downside, these rules could keep your application from updating if it is on a different major version than Dynamics...