Thanks Dagmar.
I avoided validation logic at first because my focus is on measuring the accuracy with which the users can capture, and validation logic can only prevent the gross errors. I think there are various issues at play here:
1) Repeating group is a headache. The empty screen, then having to click the New(game) key for the first row. And then at the end they keep hitting select to go the the second row, instead of going to options. Then they sometimes hit New, even though there are more options. So its not so much that they actually enter the wrong answer, they either overwrite the first set of items with the second set, or they create a third set when there are only two.
2) My issue with how to select a residential location from a list of 148. I created a hierarchy of district, town/area and farm. But the participants do not accurately know in which district the farms are - in the field the responses are usually based on the town to which the farmer takes them on Saturdays, which is not necessarily closest. For example, many farmers go into Worcester as its the biggest centre, even though it is 60 km further. So they leave the answer out as the dynamic list doesn't contain their desired answer. I've now updated the documentation with a district indicator, but it now means the users have to do a look up on a paper form before they can capture the data, but this defeats one of my objects of having a cell phone provide them with all the information. So I really don't know the answer to this.
3) less of an issue is dates and times.
a) I've tried to set mforms to use year first as that is what they are used to, but v1.3 seems to ignore this. So I've had dates captured as 20/12/1126 - this can be trapped by validation logic
b) dates with the - and times with the : - sometimes the users try to insert the - or : going round in circles trying to find them on the keyboard, and finally leaving the answer out.
c) times are captured as 24hour clock, but the answer displays on the question list as12 hr AM/PM - so they have twice captured the time as 3:00 instead of 15:00
4) In general, the continual changing of the soft key labels causes confusion, many back steps and sometimes the wrong selection.
5) The question I am really trying to answer is whether these participants who are not computer literate, many of whom do not have school leaving certificate (grade 12, standard 10, matric), can use a mobile phone to capture data accurately. Some of the terminology is 'PC' centric e.g. 'Upload Data' required a
fair deal of explanation, whereas 'Send Results' would have been more
meaningful to them.
So I'll wait and see how things pan out, and hopefully they become more skillful as they progress. It may mean I have to treat the current round as an extended training and extend the study to a further round.
Thanks again
Mike