Microsoft Business Solutions officially supports at this time Dynamics GP versions 10.0 and 9.0. Older versions: 8.0, 7.5
Great Plains Dynamics and eEnterprise 7.0 and 6.0, Dynamics and Dynamics C/S+ of versions 5.5, 5.0, 4.0, Great Plains Dynamics on Pervasive SQL 2000 or Ctree, Great Plains Accounting for DOS and Windows 9.5, 9.2, 9.1 and earlier – obviously should be either supported by Great Plains VAR, or consultant or self supported by your IT team. In this small publication we would like to review typical Dynamics GP or former Great Plains legacy version support routines:
1. Going over 2 GB MSDE database limit. This problem is attributed to Dynamics GP 7.5 and 8.0 on MSDE 2000 DB. The solution is simple – you have to call your Dynamics GP Reseller and have them request new registration key from Microsoft Dynamics subdivision of Microsoft. Even if you are currently not enrolled in Dynamics GP annual enhancement program (which might be likely the case, otherwise – why would you stick to legacy historical version of Great Plains Dynamics?). In the case when you are not sure who is your Great Plains Partner, call Microsoft directly or our office, see the phone below. New reg key should allow you to move Dynamics GP to MS SQL Server 2000 Standard. If you need Database maintenance to send DB size back below 2GB – call us for help
2. Updating Payroll Tax. If you are on SQL Server platform, you can still get tax table update. The technology is simple – we use current version of Dynamics GP 10.0 to update taxes in Dynamics database and then we copy UPR tax tables to your Dynamics database
3. Closing the year. Please, be sure you have made a backup of your Great Plains company DB, then in Routines financials, close the year. Closing the year moves open transactions in General Ledger to historical tables, which is pretty large DB reshuffling, especially if you are on Pervasive SQL 2000/Btrieve or Ctree
4. Purging history in AP, AR, GL. In Accounts Payable module transactions, such as Vendor invoice and your Payment go to history automatically when you apply payments and credit memos to invoices and debit memos. Then they are ready for history purge. In Accounts Receivables – transactions stay in open tables, even upon applying Payments to Invoices. Transaction purge helps you to meet free hard disk space requirements for older Windows Servers. Purging history is available in Utilities menu
5. Legacy Great Plains support nationwide. We specialize in such a service and we serve you nationwide via web sessions, VPN and remote connections
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
