|
|
| Line 13: |
Line 13: |
| * <code>" WHERE ([Admit_DtTm]<=" & LabDtTm_str & ") AND (" & LabDtTm_str & "<=nz([Dispo_DtTm],now())) "</code> | | * <code>" WHERE ([Admit_DtTm]<=" & LabDtTm_str & ") AND (" & LabDtTm_str & "<=nz([Dispo_DtTm],now())) "</code> |
| ** ie we start the range with the [[Admit DtTm]] | | ** ie we start the range with the [[Admit DtTm]] |
| {{DJ |
| | |
| * We should change this; however, do we only change it going forward or do we also re-import back data? Julie is about to re-import back data until 2019-01-01, so maybe we should reimport back data for all that far?
| |
| ** shouldn't it be ''Accept_DtTm'' and use ''Arrive_DtTm'' if ''[Accept_DtTm'' is blank. We have discussed that in the Project Boarding Loc, we can still determine the counts in between ''Accept_DtTm'' and ''Arrive_DtTm'' if needed. --[[User:JMojica|JMojica]] 10:25, 2019 December 10 (CST)
| |
| *** That is pretty much what I mean, it should be as you say. Do we want to do this going back in data as you re-import, or just going forward for future imports? Ttenbergen 09:41, 2019 December 11 (CST)
| |
| **** Yes going forward. also this time using first service dttm. --[[User:JMojica|JMojica]] 16:36, 2022 February 16 (CST)
| |
| ***** As in, use the ''Admit DtTm'' with the definition we have decided in there, right? [[User:Ttenbergen|Ttenbergen]] 19:48, 2022 February 17 (CST)
| |
| ****** I have changed this to use the new [[Admit DtTm]]; if that addresses this issue, pls delete, otherwise explain. [[User:Ttenbergen|Ttenbergen]] 14:06, 2022 June 1 (CDT)
| |
| }}
| |
|
| |
|
| === date constraints === | | === date constraints === |