If you're stuck on v10, then I'd suggest avoiding this technique, as there's a bug around the ordering of the last two columns of the last row of the page. This is fixed in 11.8 and above. Datawatch Modeler also supports 100 columns, not the old limit of 40.
Are you planning to run this process in an automated way or just manually? Do you need it to be verified? If you build it, who has to support it? Have your other users got the Monarch skills to confidently debug and adapt models using Column()?
If you're building a critical business process around the handling of these reports, it might be worth looking at some of other issues that are involved, and not simply at the technique of treating the missing detail problem using the multi-column region.
v 11.8. We are a maintenance paying client through 2014. The talks of migrating to v 12 in a production environment will continue to grow into the new year as deliveries continue to occur.
The limit has been given to me of 20 records at any given time.
Automated fashion. As the builder I will be the supporter moving forward...with hopes of support company wide ...with success.
I will be looking into a one on one consultation with a Monarch professional down the road. If we are to deliver our results to our clients using Monarch's capabilities the training as an entity will become easier to justify.