Differences

This shows you the differences between two versions of the page.

--- dynamiczip:glossary:orphaned_records [2015/03/19 18:03] – external edit 127.0.0.1
+++ dynamiczip:glossary:orphaned_records [2015/06/03 22:37] (current) – conni
@@ Line 3: / Line 3: @@
 Orphaned records are records that have been severed from the GP system but still exist in the SQL table(s). You can remove orphaned records by running the [[dynamiczip:utilities:Check Links Process]].
-**__How do orphaned records occur?__**
+====How do orphaned records occur?====
-A glitch in the system may result in orphaned records. For example, if a workstation locks up during some process and has to be rebooted or if a process is stopped using the Microsoft>> Windows>> Task Manager, orphaned records might result.
+A glitch in the system may result in orphaned records. For example, if a workstation locks up during some process and has to be rebooted or if a process is stopped using the Microsoft Windows Task Manager, orphaned records might result.
 In addition, records in various tables can become orphaned after removing certain information:
   * [[dynamiczip:tables:DZ Customer Supplement table]] and [[dynamiczip:tables:DZ Customer Address Supplement table]]
-  * Records in these two tables can be orphaned when customers are deleted from Microsoft Dynamics GP.
+    * Records in these two tables can be orphaned when customers are deleted from Microsoft Dynamics GP.
   * [[dynamiczip:tables:DZ PM Taxes Work and History table]]
-  * Records in this table can be orphaned when PM Transaction History is removed.
+    * Records in this table can be orphaned when PM Transaction History is removed.
   * [[dynamiczip:tables:DZ Tax Detail Supplement table]]
-  * Records in this table can be orphaned if tax details are removed manually (rather than with DZ Remove Tax Details).
+    * Records in this table can be orphaned if tax details are removed manually (rather than with DZ Remove Tax Details).
 ----