Have you tried specifying different values for the local macros at the top of the do-file? The help file describes those macros as follows:
The do-file starts with the definitions of several local macros; these are constants that the do-file uses. For instance, local macro
`datemask'is the mask of date values in the .csv files. The local macros are automatically set to default values, but they may need to be changed depending on the data.
You may also find parts of this Forum discussion helpful.
This looks like an error message from encode, which the odkmeta do-file uses for any select field whose list contains a non-integer name. The odkmeta do-file specifies option noextend to encode; noextend checks that the variable contains only values that are present in the associated value label.
Is Elbo Sebuer one of the choices in the choices sheet of your XLSForm? Is it defined in the value label? odkmeta defines value labels toward the top of the do-file. It knows to use quotes for labels with spaces, so that shouldn't be the issue.
I also wanted to draw your attention to the Stata command set trace on, which you can use to determine which command actually resulted in the error message. It can be especially useful for a do-file with a loop. In this case, it should allow you to determine which command resulted in the error message for which dataset and variable. (You should probably also set tracedepth 1, at least to start.)
I know we've discussed the filenames that the odkmeta do-file uses, something we're still working to fix. Are there other issues that you frequently encounter?