Reconnect CFE and initial error checks: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 13: | Line 13: | ||
** [[Reconnect_check_missing_L Tables_content query]] - Generally, errors in missing are the result of a failed send, so follow [[Re-sending data]] to fix | ** [[Reconnect_check_missing_L Tables_content query]] - Generally, errors in missing are the result of a failed send, so follow [[Re-sending data]] to fix | ||
* | * If there were no errors, continue what you were doing, likely the next step of [[Centralized data Vetting Process]]: [[Pre-linking checks]] | ||
== Related articles == | == Related articles == |
Revision as of 14:46, 2022 April 5
Once you "Pull" Centralized data.mdb you need to initialise the program and make sure that you have consistent initial data.
Instructions
- click the "Re-connect Data" button
- the reconnector will
- confirm if L_Log table and L_PHI table have the same records in them. If they don't there will be an error; see Procedure when there are differences between L Log and L PHI for how to proceed
- the "Re-connect Data" button automatically runs the initial cross checks, but only shows them if errors are found. If there are errors, correct them before proceeding to the next step,
- no need to run them manually
- Reconnect_check_Completes query - Generally, errors in missing are the result of a failed send, so follow Re-sending data to fix
- Reconnect_check_orphans query - see Orphans in Centralized data.mdb for what to do about these
- Reconnect_check_missing_L Tables_content query - Generally, errors in missing are the result of a failed send, so follow Re-sending data to fix
- If there were no errors, continue what you were doing, likely the next step of Centralized data Vetting Process: Pre-linking checks
Related articles
Related articles: |