Great Plains Consultant Newsflash: All GP Dynamics Versions Support

We will begin with more recent version and will go down to history:

1.       Microsoft Dynamics GP.  In 2005 Great Plains, Navision, Axapta, Solomon and Microsoft CRM were rebranded as Microsoft Dynamics family.  Great Plains became Microsoft Dynamics GP.  In the time of rename GP version was 7.5.  Current version as of July 2009 is GP 10.0.  Microsoft Dynamics GP had also versions 9.0 and 8.0.  Beginning from 8.0 Microsoft Dynamics GP is only available for Microsoft SQL Server.  At this time you can get direct support from Microsoft Business Solutions for GP 10.0 and 9.0.  Support for older versions: 8.0, 7.5 and earlier is no longer available from MBS directly.  In order to get regularly priced MBS Dynamics GP technical support, your organization should be current in Dynamics GP annual enhancement plan – in this case you have access to CustomerSource, where you normally surf techknowledge base to fix known issues in-house.  If you are not current with annual support plan, you should ask your Dynamics GP Partner to help you, your official Dynamics GP VAR has access to your company info and knowledge base.  If you are not sure who is your Dynamics GP Reseller, please call one of your local providers or feel free to call our office

2.       Great Plains for Microsoft SQL Server.  Historical versions: 7.5, 7.0, 6.0, 5.5, 5.0, 4.0, 3.2 were available on several DB platforms: Microsoft SQL Server, Pervasive SQL/Btrieve, Ctree/Faircom.  Great Plains Tech Support for MS SQL Server is typically the most efficient, as Great Plains Consultant has full control in SQL Querying and should be able to fix your table records with SQL Update or Delete statements.  Great Plains errors usually are qualified as DB errors (Database inconsistency) and Great Plains Dexterity errors (user interface).  If you got FRx financial reporting issues, these are typically related to FRx Sysdata location and its G32 files corruption

3.       Great Plains on Pervasive SQL 2000/Btrieve and Ctree/Faircom.  Client side errors should have similar path for fixing as in #2, however database records fix is typically done via ODBC connection tools: Microsoft Access, MS SQL Server Linked Server, etc.  Please install Pervasive or Ctree ODBC driver from GP CD.  If you prefer MS Access, please create new DB and link Great Plains tables – ODBC link

4.       Great Plains Accounting for DOS and Windows.  Here you have Btrieve DB.  If you have your legacy GPA in Novell or Windows NT Server, please consider to redeploy it on Windows 2003 and Pervasive SQL 2000 SP3.  GPA is sort of black box, there are no training programs to support GPA and you should not expect on-call local Great Plains Accounting consultant support.  We have GPA legacy technical support Database with all known issues listed, so we are in good position to support your GPA or assist you in Great Plains Accounting migration to Microsoft Dynamics GP

5.       GP Upgrade Path.  It depends on the version.  We will give you long migration path from GPA for DOS 9.2 to Dynamics GP 10.0.  First step – upgrade GPA 9.2 to 9.5.  Second Step – use GPA migration tool to Great Plains 7.5 on Microsoft SQL Server, this step requires you to purchase upgrade GP licenses (typically with good discount as you are on GPA).  Third Step: Dynamics GP 7.5 – GP 9.0.  Fifth step Dynamics GP 9.0->10.0