Query send check centralized is owner: Difference between revisions
Ttenbergen (talk | contribs) m →Log |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
| DIC_summary = | | DIC_summary = Run automatically at the beginning of [[sending]] to ensure that no records that are already vetted or sent can be re-sent | ||
| DIC_related_concepts = D_ID; Pat_ID; Service/Location field | | DIC_related_concepts = D_ID; Pat_ID; Service/Location field | ||
| DIC_firmness = hard check | | DIC_firmness = hard check | ||
| Line 18: | Line 17: | ||
* a "sent" record was set back to "complete" on a collector laptop before sending | * a "sent" record was set back to "complete" on a collector laptop before sending | ||
Correct by addressing the issue. | Correct by addressing the issue. | ||
== Implementation == | |||
Component ''query L_Log_ownerCheck_maker'' makes temporary ''table L_Log_ownerCheck'' which is then compared with local [[L Log table]]. | |||
== Log == | == Log == | ||
2020-04-26 - changed component ''query L_Log_ownerCheck_maker'' to only look at [[D_ID]]s that start with this laptop's [[Laptop identifier]] | |||
2019-10-27 - changed to not include recordstatus "deleted" | 2019-10-27 - changed to not include recordstatus "deleted" | ||
2019-03-13 - tweaked query to only use relevant fields of O_L_Log, since it turns out that Access has a maximum record set size of 1GB; hopefully this will fix [[System resource exceeded]] | 2019-03-13 - tweaked query to only use relevant fields of O_L_Log, since it turns out that Access has a maximum record set size of 1GB; hopefully this will fix [[System resource exceeded]] | ||
Revision as of 20:07, 26 April 2020
| Data Integrity Checks | |
| Summary: | Run automatically at the beginning of sending to ensure that no records that are already vetted or sent can be re-sent |
| Related: | D_ID, Pat_ID, Service/Location field |
| Firmness: | hard check |
| Timing: | |
| App: | CCMDB.accdb |
| Coding: | Query send_check_centralized_is_owner |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | 2016-01-01 |
| Backlogged: | true |
Approximate implementation date
This query will usually trigger if
- an earlier combination of Pat_ID and Service/Location is accidentally re-used on a collector laptop (e.g. should enter HSC_A1-1000 but entered HSC_A1-100)
- something went wrong during a previous send and records were not set to "sent" or "completed" properly
- a "sent" record was set back to "complete" on a collector laptop before sending
Correct by addressing the issue.
Implementation
Component query L_Log_ownerCheck_maker makes temporary table L_Log_ownerCheck which is then compared with local L Log table.
Log
2020-04-26 - changed component query L_Log_ownerCheck_maker to only look at D_IDs that start with this laptop's Laptop identifier 2019-10-27 - changed to not include recordstatus "deleted" 2019-03-13 - tweaked query to only use relevant fields of O_L_Log, since it turns out that Access has a maximum record set size of 1GB; hopefully this will fix System resource exceeded 2019-03 Around this time the STB_MedB laptop had >200 records on it and was getting System resource exceeded errors. The errors were happening when this query was run.
Related articles
| Related articles: |