MWSTR Orphans - due to PowerTools usage?
Posted: Thu May 01, 2008 1:44 pm
I was checking the integrity of some of our Medisoft tables and ran the following query in ARC32:
Select *
From MWSTR as A
Where A.\"chart number\" NOT IN
(Select B.\"chart number\"
From MWPAT as B
Where A.\"chart number\" = B.\"chart number\")
It turned up 115 MWSTR rows (records) whose Chart Number have no match in MWPAT.
I ran similar queries against the other tables that reference the 'Chart Number' key and found no orphans.
We have been using PowerTools for some time to correct the occasional mistyped Chart Number. My best guess is that perhaps PowerTools neglects to update this one table? Has anyone else used PowerTools quite a bit and also has orphaned MWSTR records? How critical are entries in the MWSTR table?
Thank you sincerely.
Paul Williams
Select *
From MWSTR as A
Where A.\"chart number\" NOT IN
(Select B.\"chart number\"
From MWPAT as B
Where A.\"chart number\" = B.\"chart number\")
It turned up 115 MWSTR rows (records) whose Chart Number have no match in MWPAT.
I ran similar queries against the other tables that reference the 'Chart Number' key and found no orphans.
We have been using PowerTools for some time to correct the occasional mistyped Chart Number. My best guess is that perhaps PowerTools neglects to update this one table? Has anyone else used PowerTools quite a bit and also has orphaned MWSTR records? How critical are entries in the MWSTR table?
Thank you sincerely.
Paul Williams