Manager

Manager program.
Tasklist

FS#148 - Time field in EpiData Manager

Attached to Project: Manager
Opened by Hans L Rieder (hansrieder) - Thursday, 07 May 2015, 08:19 GMT
Last edited by Torsten Bonde Christiansen (torstenchr) - Wednesday, 17 June 2015, 12:12 GMT
Task Type Bug Report
Category Drag & Drop
Status Waiting on Feedback
Assigned To Torsten Bonde Christiansen (torstenchr)
Operating System All
Severity Low
Priority Normal
Reported Version 2.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

EpiData Manager
Program Version: 2.0.2.28 r1115
Core version: 2.0.0.0 r1126
FPC Version: 2.6.4
Platform: x86_64-Win64

I have a time field on opening a new record and a time field on first save.

1) It is unclear where and how to put the interval calculation, if the second to last field is one that either jumps to save record or goes to the last field
2) In analysis, the two fields are read as floats and have the form 0.852616. It is not clear what this is. Assuming that it could be a fraction of the day (as in EpiData Entry 3.1), I multiply (end-start)*86400 but the result does not make sense, giving something like 22.98 up to 73.01. I doubt that I took that many seconds (should be more like in the order of 10 seconds per record)
This task depends upon

Comment by Torsten Bonde Christiansen (torstenchr) - Wednesday, 17 June 2015, 12:11 GMT
Ad 1)
It is not posible to have interval calculation during entry if one of the fields involved are updated "post" entry (after record). The current way calculation works is solely by performing calculations when leaving the field (after entry). But since such a field is never entered and left, the calculation is not performed.

Ad 2)
The value is (as you note) a fraction of the day with 00:00:00 = 0.0 and 24:00:00 = 1.0 (i am fully aware that 24:00:00 is not a valid clock, but the program is capable of handling continuos time passing a day). Regarding the number of seconds passed it is not posible to say anything meaningfull without knowing the setup of your system. A relative slow computer may record the "new record" time before the dataform is fully ready for entry, accounting for the slight delay in numbers.

Loading...