PL 2Phin Fake or Blank: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Data Integrity Check}} | {{Data Integrity Check | ||
|DIC_summary=Finds blank [[PHIN]]s and those entered to meet [[function Validate_PHIN]] so [[Data Processor]] can apply [[PseudoPHIN]] via [[Generating PseudoPHINs]]. | |||
|DIC_related_concepts=PHIN field | |||
|DIC_firmness=hard check | |||
|DIC_coding=query ''PL_2Phin_Fake_or_Blank'' | |||
|DIC_status=implemented | |||
|DIC_LProblem=no | |||
|DIC_app=Centralized data front end.accdb | |||
|DIC_backlogged=No | |||
}} | |||
=== [["cannot open any more tables" in Access]] === | |||
See [["cannot open any more tables" in Access]] | |||
=== Can't limit this to [[RecordStatus]] completes/sent === | |||
This query is used for [[Generating PseudoPHINs]]. One requirement there is to make sure that no PHINs are currently < 100000000, '''even incompletes''', since having one of those would mess up our incrementing for [[PseudoPHIN]]s. So, this query needs to include incompletes, even if they won't ''usually'' need to be acted on. | |||
== Related articles == | == Related articles == | ||
Line 5: | Line 20: | ||
[[Category:Registry checks]] | [[Category:Registry checks]] | ||
[[Category:PL queries]] | |||
[[Category:Data Processing]] |
Latest revision as of 12:12, 2022 December 7
Data Integrity Checks | |
Summary: | Finds blank PHINs and those entered to meet function Validate_PHIN so Data Processor can apply PseudoPHIN via Generating PseudoPHINs. |
Related: | PHIN field |
Firmness: | hard check |
Timing: | always |
App: | Centralized data front end.accdb |
Coding: | query PL_2Phin_Fake_or_Blank |
Uses L Problem table: | no |
Status: | implemented |
Implementation Date: | not entered |
Backlogged: | No |
"cannot open any more tables" in Access
See "cannot open any more tables" in Access
Can't limit this to RecordStatus completes/sent
This query is used for Generating PseudoPHINs. One requirement there is to make sure that no PHINs are currently < 100000000, even incompletes, since having one of those would mess up our incrementing for PseudoPHINs. So, this query needs to include incompletes, even if they won't usually need to be acted on.
Related articles
Related articles: |