last changes

Author: haywoodsloan

support/dynamics/gp/information-about-new-connection-objects-vba.md

@@ -56,7 +56,3 @@ cn.DefaultDatabase = UserInfoGet.IntercompanyID
 cmd.ActiveConnection = cn
 End Sub
 ```
-
-## References
-
-[How to use the new RetrieveGlobals9.dll file in Integration Manager and in Microsoft Dynamics GP 9.0](https://support.microsoft.com/help/913341)

support/dynamics/gp/key-segment-not-found.md

@@ -60,11 +60,11 @@ After the patch or update has been installed and these messages happen, follow t
 
 7. Exit Microsoft Dynamics GP.
 
-8. Recreate the Reports.dic using the steps in [KB 850465 - How to re-create the Reports.dic file in Microsoft Dynamics GP](https://support.microsoft.com/help/850465).
+8. Recreate the Reports.dic using the steps in [How to re-create the Reports.dic file in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/how-to-re-create-the-reports-dot-dic-file).
 
     > [!NOTE]
     > In step 3 of KB 850465, use the instructions after step 3 to import the modified reports back in using the Report Writer method. If that doesn't work, then try the steps listed in step 3 for the Customization Maintenance method.
 
 9. Test again.
 
-10. If there are also modified forms, use [How to re-create the Forms.dic file in Microsoft Dynamics GP](https://support.microsoft.com/help/951767) to recreate the Forms.Dic as well.
+10. If there are also modified forms, use [How to re-create the Forms.dic file in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/re-create-the-forms-dot-dic-file) to recreate the Forms.Dic as well.

support/dynamics/gp/last-year-end-update-field-is-not-updated.md

@@ -69,4 +69,4 @@ To resolve this issue, follow these steps:
 ## More information
 
 For more information about the tax fields and year-end update fields in US Payroll in Microsoft Dynamics GP, see
-[Information about the tax fields and year-end update fields in Payroll in Microsoft Dynamics GP](https://support.microsoft.com/help/949154).
+[Information about the tax fields and year-end update fields in Payroll in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/tax-fields-year-end-update-fields).

support/dynamics/gp/prevent-zero-dollar-remittances-from-printing.md

@@ -23,13 +23,9 @@ This article discusses how to prevent zero dollar remittances from printing in P
 > [!NOTE]
 > To prevent zero dollar remittances from printing, you must have administrator access to Microsoft Dynamics GP and the instance of Microsoft SQL Server.
 
-For more information about how manual payments appear on the check stub and when they're removed from the PM20000 table and from the PM20100 table, click the following article number to view the article in the Microsoft Knowledge Base:
+For more information about how manual payments appear on the check stub and when they're removed from the PM20000 table and from the PM20100 table, see [Information about how manual payments, credit memos, and returns appear on the check stub when you run the Select Checks process in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/how-manual-payments-credit-memos-appear).
 
-[860395](https://support.microsoft.com/help/860395) Information about how manual payments appear on the check stub and when they're removed from the PM20000 table and from the PM20100 table when you run the Select Checks process in Microsoft Dynamics GP  
-
-For more information about how payments that have amounts of zero are treated in Payables Management, click the following article number to view the article in the Microsoft Knowledge Base:
-
-[861276](https://support.microsoft.com/help/861276) How payments that have amounts of zero are treated in Payables Management in Microsoft Dynamics GP  
+For more information about how payments that have amounts of zero are treated in Payables Management, see [How payments that have amounts of zero are treated in Payables Management in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/how-payments-that-have-zero-are-treated).
 
 ## Steps to prevent zero dollar remittances from printing
 

support/dynamics/gp/problem-starting-up-report.md

@@ -64,4 +64,4 @@ If the REPORTS.DIC file doesn't exist in that location, use one of the following
 
 Re-create the REPORTS.DIC file.
 
-For more information about how to do it, see [How to re-create the Reports.dic file in Microsoft Dynamics GP](https://support.microsoft.com/help/850465).
+For more information about how to do it, see [How to re-create the Reports.dic file in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/how-to-re-create-the-reports-dot-dic-file).

support/dynamics/gp/re-create-the-forms-dot-dic-file.md

@@ -56,4 +56,4 @@ Rename the existing Forms.dic file to save it as a backup. To do it, follow thes
 
 ## More information  
 
-To recreate the Reports.dic file, see the steps in [How to re-create the Reports.dic file in Microsoft Dynamics GP](https://support.microsoft.com/help/850465).
+To recreate the Reports.dic file, see the steps in [How to re-create the Reports.dic file in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/how-to-re-create-the-reports-dot-dic-file).

support/dynamics/gp/return-code-17-messages.md

@@ -56,9 +56,8 @@ To resolve this problem, follow these steps:
 > Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.
 >
 > You may want to use a test company database that has a copy of live company data. When you do this, users will not have to log off from Microsoft Dynamics GP or from Microsoft Great Plains 8.0 while you test the steps to resolve these issues. After you have tested the steps, you can process these steps against the live company data after all the users have logged off at the end of the workday.
-For more information, click the following article number to view the article in the Microsoft Knowledge Base:
 >
-> [871973](https://support.microsoft.com/help/871973) How to set up a test company that has a copy of live company data by using SQL Server 7.0, SQL Server 2000, or SQL Server 2005  
+> For more information, see [Set up a test company that has a copy of live company data for Microsoft Dynamics GP by using Microsoft SQL Server](/troubleshoot/dynamics/gp/set-up-a-test-company).
 
 ### Step 1: Back up the company database
 

support/dynamics/gp/set-up-development-environment-when-using-dexterity.md

@@ -24,7 +24,7 @@ To follow the steps in this article, you must be able to see the file name exten
 1. On the **Tools** menu, click **Folder Options**.
 2. In the **Folder Options** dialog box, click the **View** tab, and then click to clear the **Hide extensions for known file types** check box.
 
-The steps in this article assume that you already have a product ID for the project that you develop. For more information about product IDs for Dexterity, see [Description of product IDs for Dexterity in Microsoft Dynamics GP](https://support.microsoft.com/help/914899).
+The steps in this article assume that you already have a product ID for the project that you develop. For more information about product IDs for Dexterity, see [Description of product IDs for Dexterity in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/description-product-ids-dexterity).
 
 For more information about how to request a product ID for Dexterity, see [How to request a new Dexterity product ID for my product](https://support.microsoft.com/help/867102).
 
@@ -134,7 +134,7 @@ To set up the development environment, follow these steps:
 
     7. To update the source control state of the resources in the dictionary, click **Source Control** on the **Explorer** menu, and then click **Update SCC State**.
 
-    8. If you use the Dexterity source control functionality, create an index file to control the resource ID between builds. For more information about how to use an index file and the Dexterity source control functionality, see [How to use an index file and the Great Plains Dexterity source code control functionality to make sure that the resources that you create maintain the same resource ID in different builds and versions of your code](https://support.microsoft.com/help/894699).
+    8. If you use the Dexterity source control functionality, create an index file to control the resource ID between builds. For more information about how to use an index file and the Dexterity source control functionality, see [How to use an index file with Dexterity to ensure resource IDs do not change in new builds and versions](/troubleshoot/dynamics/gp/how-to-use-index-file-with-dexterity-to-maintain-resource-ids-in-new-builds-and-versions).
 
 9. Create a macro of the chunking process.
 
@@ -155,7 +155,7 @@ To set up the development environment, follow these steps:
     6. Close the destination dictionary.
     7. Create a chunk file.
 
-        For more information about how to create a chunk file in Dexterity, see [How to create a chunk file in Great Plains 8.0 Dexterity](https://support.microsoft.com/help/894700).
+        For more information about how to create a chunk file in Dexterity, see [How to create a chunk file in Dexterity in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/create-a-chunk-file-dexterity).
 
         Use the following naming conventions:
           - Extracted dictionary: C:\\Dex1000\\Project\\Project.dic

support/dynamics/gp/the-compatibility-modules-features.md

@@ -54,4 +54,4 @@ Additionally, you can contact Technical Support for Microsoft Dynamics and relat
 
 ## References
 
-For more information about the compatibility of Fixed Asset Management with Project Accounting, see [How to integrate Project Accounting with Fixed Asset Management in Microsoft Dynamics GP](https://support.microsoft.com/help/936276).
+For more information about the compatibility of Fixed Asset Management with Project Accounting, see [How to integrate Project Accounting with Fixed Asset Management in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/integrate-project-accounting-with-fixed-asset-management).

support/dynamics/gp/the-year-end-closing-procedures.md

@@ -29,7 +29,7 @@ To do it, follow the steps:
 
 ### Step 1: Do all the year-end closing procedures for Payables Management in Microsoft Dynamics GP
 
-Close Payables Management first. This action guarantees that all the outstanding fixed asset transactions are capitalized. For more information about closing Payables Management, see [KB -Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP](https://support.microsoft.com/help/875169).
+Close Payables Management first. This action guarantees that all the outstanding fixed asset transactions are capitalized. For more information about closing Payables Management, see [Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP](/troubleshoot/dynamics/gp/year-end-closing-payables-management).
 
 ### Step 2: Enter all the fixed asset transactions for the current fiscal year