If you have Microsoft Dynamics GP implemented in your organization and you are currently on one of the old versions: 8.0, 7.5, 7.0, 6.0, 5.5, 5.0, 4.0, Great Plains Dynamics on Pervasive SQL Server 2000/Btrieve or Ctree (version 7.5 and below) or Great Plains Accounting for DOS or Windows: 9.5, 9.2 or earlier, you should consider Great Plains version update or at least moving existing version from old hardware to the new Windows 2003 or 2008 server.
In some situations you may just need to reactivate Great Plains for auditing purposes. If you have current annual support plan through your official Dynamics GP Reseller, you should have access to newest version registration key: Dynamics GP 10.0 and plan your upgrade with your Great Plains Partner. For the rest of you, please, read these highlights to get orientation:
1. Microsoft Business Solutions annual support plan and when did it expire for your organization. If you plan expired, you do not longer have access to your Microsoft Customer Source, where you existing customers have access to Knowledge Base, and your registration keys. However, even if you do not have support to Customer Source, your Dynamics GP VAR should have and these people should see your records. If you are not sure who is your Great Plains Partner, please consider calling Microsoft or try fresh start and locate new Dynamics GP Service Provider, who fits your criteria: your industry expertise, technology versus CPA oriented or vice versa, local with reasonable experience version nationwide with broad expertise to give you few criteria determination ideas
2. Get reenrolled to GP annual enhancement program or wait. If you are on really archaic version of Great Plains, such as 6.0 or earlier, it might be challenging to pay for reenrollment, at least for some of you. However, the chances are that your organization owns reg key of newer version. Have you current or newly selected Dynamics GP VAR to check this for you. For example, if you are on version 6.0, your organization may own reg key for Dynamics GP 7.5 or even 8.0. Version 8.0 is pretty robust, and instead of staying on Great Plains 6.0 without support (as it is unlikely that Dynamics GP consultants are maintaining their old knowledge) you may move couple of steps up to Great Plains 8.0
3. Great Plains Update Path. If you are on GP 8.0 or 9.0 – this is not a concern, as upgrade from these versions might be accomplished in just one step (assuming , that you applied required 8.0 SP5 and upgrading to Dynamics GP 10.0 you applied SP2 or 3). If you are on older version, please first discuss Great Plains Upgrade strategy with your consultant, and do not try to insert GP 10.0 CD, obtained from evaluation programs, such as MSDN, for example. Old versions are upgraded in two or more steps, coming through intermediary version. Example, upgrading from Great Plains 6.0 to 10.0 – first you move 6.0 to 7.5, then you upgrade 7.5 to 9.0 and final step to 10.0
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
