Reconnect check Completes query: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
|DIC_implementation_date=2022-03-24 | |DIC_implementation_date=2022-03-24 | ||
|DIC_status=implemented | |DIC_status=implemented | ||
|DIC_LProblem= | |DIC_LProblem=No | ||
|DIC_app=Centralized data front end.accdb | |DIC_app=Centralized data front end.accdb | ||
|DIC_backlogged=No | |DIC_backlogged=No | ||
Latest revision as of 22:04, 22 July 2025
| Data Integrity Checks | |
| Summary: | Shows any records in that have RecordStatus "Complete", indicating failed send. |
| Related: | RecordStatus, sending |
| Firmness: | hard check |
| Timing: | complete |
| App: | Centralized data front end.accdb |
| Coding: | Reconnect check Completes query |
| Uses L Problem table: | No |
| Status: | implemented |
| Implementation Date: | 2022-03-24 |
| Backlogged: | No |
The Reconnect_check_Completes query in CFE that lists pts with RecordStatus "Complete". It shows up if such files are encountered when "Re-connect Data" button is pressed.
Instructions
If this query triggers, usually the laptop that sent the offending records will need to re-send.
Related articles
| Related articles: |