Query check tmp generate allowed: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 11: | Line 11: | ||
In spite of the name, this function is not a check funtion. It is called by Sub ''GenerUpdate_tmp_entry'' which is used by the [[overstay]] project to generate colour entries in tmp. | In spite of the name, this function is not a check funtion. It is called by Sub ''GenerUpdate_tmp_entry'' which is used by the [[overstay]] project to generate colour entries in tmp. | ||
{{DT | Needs to be cleaned up now that Overstay is done. }} | |||
== Related articles == | == Related articles == | ||
Revision as of 12:08, 2 March 2020
| Data Integrity Checks | |
| Summary: | check that tmp project/item combo exists for this location in Overstay |
| Related: | Overstay, Overstay Predictor Project |
| Firmness: | hard check |
| Timing: | |
| App: | CCMDB.accdb |
| Coding: | query check tmp generate allowed, Sub GenerUpdate_tmp_entry |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | date change was rolled out / first applied |
| Backlogged: | true |
In spite of the name, this function is not a check funtion. It is called by Sub GenerUpdate_tmp_entry which is used by the overstay project to generate colour entries in tmp.
|
Needs to be cleaned up now that Overstay is done. |
Related articles
| Related articles: |