Query check tmp generate allowed: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) m not retired after all, it's used for more than overstay |
||
| Line 5: | Line 5: | ||
|DIC_coding=query ''check tmp generate allowed'', Sub ''GenerUpdate_tmp_entry'' | |DIC_coding=query ''check tmp generate allowed'', Sub ''GenerUpdate_tmp_entry'' | ||
|DIC_implementation_date=date change was rolled out / first applied | |DIC_implementation_date=date change was rolled out / first applied | ||
|DIC_status= | |DIC_status=implemented | ||
|DIC_app=CCMDB.accdb | |DIC_app=CCMDB.accdb | ||
|DIC_backlogged=No | |DIC_backlogged=No | ||
Revision as of 10:07, 9 April 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: | always |
| 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: | No |
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.
Related articles
| Related articles: |