Query send check centralized is owner: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m Text replacement - "CCMDB.mdb" to "CCMDB.accdb" |
||
| Line 5: | Line 5: | ||
| DIC_firmness = hard check | | DIC_firmness = hard check | ||
| DIC_timing = | | DIC_timing = | ||
| DIC_app = CCMDB. | | DIC_app = CCMDB.accdb | ||
| DIC_coding = Query ''send_check_centralized_is_owner'' | | DIC_coding = Query ''send_check_centralized_is_owner'' | ||
| DIC_status = implemented | | DIC_status = implemented | ||
Revision as of 12:01, 22 September 2019
| 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.
Log
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: |