Query send check centralized is owner

From CCMDB Wiki
Revision as of 13:27, 2019 March 13 by Ttenbergen (talk | contribs)
Jump to navigation Jump to search
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.mdb
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
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. 
  • Categories: 
  • form:

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: