| At this time (fall of 2007) Microsoft | | | | be verified: POP10110, POP10310, POP30110 and |
| Dynamics GP customers are actively upgrading | | | | POP30310 - they store purchase orders and |
| to GP version 9.0 and initial upgrades are | | | | receipts lines. Microsoft recommends doing |
| performed to Microsoft Dynamics GP 10.0. | | | | checklinks, prior to upgrade process, however |
| Version 10.0 will be in more active upgrade | | | | we saw situations, where potentially check |
| mode, when Microsoft will release GP 10.0 | | | | links don't do all the orphans cleaning job. |
| Service Pack 1, as current GP 10.0 upgrade | | | | If check links doesn't help, please construct |
| path is limited to 8.0 SP5 and 9.0 SP2. | | | | the script which will give you orphans in |
| | | | lines table, similar to the following: select |
| Having reasonable number of GP version | | | | a.* from POP10110 a left join POP10100 b on |
| updates performed, we would like to share | | | | a.PONUMBER=b.PONUMBER where b.PONUMBER is |
| experience. Lets' start with the most | | | | null. And again, prior to rescuing to |
| popular upgrade to 9.0. | | | | scripting, you should try check links |
| | | | approach. |
| 1. As versions 8.0, 7.5, 6.0, and earlier are | | | | |
| discontinued for Microsoft Dynamics technical | | | | 3. If after check links, upgrade failed on |
| support, you should consider this bell as | | | | POP tables, you will have to restore DYNAMICS |
| strong signal to walk away from these older | | | | and all Companies DB to initial version and |
| versions. Versions 7.5 and older were | | | | try data repair with scripting. Then design |
| available on MS SQL Server as well as on | | | | delete scripts with your DBA person. |
| Pervasive SQL 2000 (former Btrieve) and | | | | Microsoft partner should be able to apply |
| Ctree. In the case when you are on non-MS | | | | failed company rolling back script, so you do |
| SQL Server DB - you will have to undergo | | | | not have to start from initial version for |
| migration step to SQL Server based version. | | | | all the databases, however this script is |
| Assuming that your case is straight forward, | | | | confidential. |
| let's move on and review known version | | | | |
| upgrade issues | | | | 4. Other potentially problem tables. We've |
| | | | also seen the problem with IV10200 table. In |
| 2. Purchase Order Processing tables problems. | | | | version 9.0 inventory valuation formula was |
| If you are using POP module, then you must | | | | revised and it now relies on IV10200 to |
| check you Purchase Orders and Receipts work | | | | higher extent. In some cases this table |
| and historical tables on the subject of | | | | conversion script fails and upgrading |
| so-called orphan lines. These tables should | | | | application freezes. |