Microsoft Dynamics GP 7.5, 9.0 version update notes

When talking about Corporate ERP application upgrade, it is always a good idea to check with your Microsoft Dynamics GP Partner, as time is going on and new versions or Service packs should or could be released, this article is intended to give you the idea about the steps and provide some initial comfort level on Great Plains version upgrade decision making.  Upgrade is possible for all Great Plains versions, including Great Plains Accounting for DOS and Windows (if this is your case or if you are on Great Plains Dynamics on Pervasive SQL 2000/Btrieve or Ctree/Faircom, please review our earlier publications), however in this article we will concentrate on Microsoft Dynamics GP version 7.5, 8.0 and 9.0 upgrade to Dynamics GP 10.0 (current version as of December 2009, new version Microsoft Dynamics GP 11.0 should be released in May 2010)
1. Microsoft Great Plains 7.5 upgrade.  This version was renamed (or possibly to say rebranded) into Microsoft Dynamics GP 7.5.  If you install it from original CD - it will be named as Microsoft Business Solutions Great Plains.  if you are MBS Great Plains 7.5, there are two ways to update to Dynamics GP 10.0, where both have two steps.  First way (we recommend it as Dynamics GP 9.0 is still supported by Microsoft Business Solutions and you can see more recent service packs, supposedly fixing problems with upgrade).  Second way is upgrade to Microsoft Dynamics GP 8.0 first and then apply GP 8.0 SP 4.0 (MBS is no longer supporting Dynamics GP version 8.0, and some of the upgrade fixes might not be reflected in abandoned Dynamics GP 8.0 version and its service packs).  And Second step is to upgrade from Dynamics GP 9.0 (or 8.0) to GP 10.0.  Please, note that you cannot just insert Dynamics GP 10.0 CD1 (without incorporated Service packs), first step is to install Dynamics GP workstation from SD1 of GP10.0 and then apply Service Pack (4 or 3).  Please, note that Microsoft Dynamics GP 10.0 has new security model, based on Security Roles, security conversion was successfully implemented with Dynamics GP 10.0 Service Pack 1 (we are a bit conservative and would like to say, that there were issues up to Dynamics GP 10.0 Service Pack 3)
2. Microsoft Dynamics GP 8.0 upgrade.  If you are already on Microsoft Dynamics GP version 8.0, you will need just one step to get updated to GP version 10.0.  Dynamics GP 10.0 with Service Pack 3 DVD should do the job (available to download from MSDN or your Partner or Customer Source).  There is no need for you to upgrade to Dynamics GP 9.0, as you can go directly to Microsoft Dynamics GP 10.0
3. Upgrading from Microsoft Dynamics GP 9.0 to 10.0.  This upgrade is especially sensitive to Service Packs.  Do not expect simply to insert GP 10.0 CD1 into DC drive and begin upgrade process - upgrade requires Service Packs matching list for GP 9.0 and for GP 10.0.  In this article we would like to share with you one substantial Microsoft Dynamics GP 10.0 upgrade issue, when you are downloading Dynamics GP 10.0 DVD with Service Pack 3 incorporated**ISSUE RESOLVED**This issue is resolved with Microsoft Dynamics GP 10.0 Service Pack 4.  Install Service Pack 4 prior to launching Microsoft Dynamics GP 10.0 Utilities for the update to resolve the issue. Click HERE to download Service Pack 4.
If you are updating from Microsoft Dynamics GP 9.0 with version 9.00.0337 or later and using Microsoft SQL Server 2000, the SEE30303 table will fail with the error "[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near '('." This table is for the Historical Inventory Trial Balance (HITB) product.  Even if you do not use the product, the update will fail as it is installed by default.  This issue will be addressed in an upcoming service pack.  Refer to the workaround steps below:
a. Do not restore the company database.  Leave the company database at the failed state.b. Close Microsoft Dynamics GP 10.0 Utilities.c. Run the following script in Query Analyzer:
UPDATE DYNAMICS..DU000030 set Status = 0, errornum=0 where fileNumber = 1 and PRODID = 5597
d. Run the following script in Query Analyzer to create the required index on the SEE30303 table:
CREATE UNIQUE CLUSTERED INDEX [AK5SEE30303] ON [dbo].[SEE30303] ( [GLPOSTDT] ASC, [ITEMNMBR] ASC, [QTYTYPE] ASC,[SEQNUMBR] ASC )
By the way, the issue above is reported to be resolved in Microsoft Dynamics GP Service Pack 4