Hi all, I would like to restrain field staff from accidentaly typing a time
value that is higher than or lower than a previous time value entered.
For example if a client arrived at 7.30AM EAT and is being registered at
7.30AM EAT or latter say 9.00AM EAT, the registration time should not be
less than 7.30AM but can be equal to or greater than 7.30AM EAT. Lkewise
the arrival time should not be greater than the registration time.
Thanks.
-Saduma
Hi Saduma,
Time calculation in ODK using the time widget is not robust as we'd like.
My recommendation is to use an integer or select one widget for hours
and another for minutes. Then take those values and do the appropriate
calculation (hours*60+minutes) to compare arrival time with
registration time.
Yaw
ยทยทยท
-- Need ODK consultants? Nafundi provides form design, server setup, in-field training, and software development for ODK. Go to https://nafundi.com to get started.On Thu, Nov 12, 2015 at 5:30 PM, Saduma Ibrahim sirahimahs@gmail.com wrote:
Hi all, I would like to restrain field staff from accidentaly typing a time
value that is higher than or lower than a previous time value entered.
For example if a client arrived at 7.30AM EAT and is being registered at
7.30AM EAT or latter say 9.00AM EAT, the registration time should not be
less than 7.30AM but can be equal to or greater than 7.30AM EAT. Lkewise the
arrival time should not be greater than the registration time.
Thanks.
-Saduma--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.