Force Close on Save

[GoogleCodeExporter]

with so many questions, the save can have a lot of work. Once in a
couple hundred surveys one of the androids will show the Force Close
error when you "save as complete". In actuality, as far as I can tell,
it never loses the data. Solution is nothing, just move on to the next
survey.

Additional symptom: When the force close on save occurs, data can drift into 
the 
wrong node. Here, K17 is a select1 with options 1,0, or 66 possible. In this 
example 
taken from an force close on save episode, the date from another multi select 
question has been written into this node. 
<k17>1 3</k17> 

Original issue reported on code.google.com by yanokwa on 29 Apr 2010 at 10:29

[GoogleCodeExporter]

Original comment by mitchellsundt@gmail.com on 21 Oct 2011 at 8:21

• Added labels: Collect

[GoogleCodeExporter]

there was a javarosa bug where data would be written into another node. this 
has been fixed.

Original comment by yanokwa on 2 Nov 2011 at 1:50

• Changed state: Fixed