The touch-screen-mode ON requires a different UI rendering as the OFF mode and it seems that there are some restrictions. Personally I'm not surprised that there are errors by 400 columns which aren't any useful within the UI - with or without touch - because nobody could really work with it. Quite probably it's just to export it for another tool.
I think you have already found the most simple solution by disabling the touch.
Nevertheless I suggest to move this export-job to the script to store the table as csv and/or to consider to transform the data-structure. I assume that the data are a crosstable and such structure could be easily transformed with the crosstable load-prefix.
The touch-screen-mode ON requires a different UI rendering as the OFF mode and it seems that there are some restrictions. Personally I'm not surprised that there are errors by 400 columns which aren't any useful within the UI - with or without touch - because nobody could really work with it. Quite probably it's just to export it for another tool.
I think you have already found the most simple solution by disabling the touch.
Nevertheless I suggest to move this export-job to the script to store the table as csv and/or to consider to transform the data-structure. I assume that the data are a crosstable and such structure could be easily transformed with the crosstable load-prefix.
I agree the table in question isn't appropriate and is a step change from a worse position, and before a more suitable solution, but was a highlight for the question.
Was interested in the differences between the 2 modes and any specific limitations as was unaware of any between modes.
I don't know how the rendering of these sites worked but I think the most parts are the same in ON/OFF unless the user interaction layer. The zooming is different and also the ways to access any object and the parts within the objects and here it seems to result in an overflow.
