Just to answer the questions...
This is Prime 4.0, and I've not seen such problems before in v.15 or prior.
By displaying the array, I mean toggling off the button Collapse Nested Arrays. When trying, it threw an exception and forced me to close MathCAD. This repeated over and over again until I deleted and recreated the array region, suggesting that region was corrupted.
This was a simple READCSV file command, but doubt that has any thing to do with it once read. I restarted, opened a new file and did some testing, and found no serious limit to the size of the or displaying the array. However, I still had problems reading the array from within the parent worksheet. Somehow, MathCAD appeared to corrupt the child worksheet, and each such wierd instance seemed to be associated with the include function in the parent worksheet.
After a few hours sleuthing the problem, I gave up on using the include, writing the results off to an output file, and reading back in where I needed it. I noticed a few issues using include, some workable, but others still a mystery:
1) A completely functioning standalone child or grandchild worksheet has to be careful with relative paths when being called by a parent. The parent will execute the statements from the perspective of its own path. (user beware?) Static paths aren't the solution, and neither is putting them within a common directory. However, even when the directory paths are deconflicted, there are still other problems. *Some path functions are needed in MathCAD, defined dynamically, not statically by the user*
2) When including multiple child worksheets into a parent, the children could have problems with array variables with a common name. You would think that the latter would overwrite the former, which I didn't care about, so long as the aforementioned array output (uniquely named) could be transferred... But there still seemed to be problems indexing the arrays that already existed from a previous included worksheets. *This is a serious problem with using includes*. I was trying to use multiple copies of a worksheet acting on different data sets, but they seem to stumble on each other despite being sequential.
3) The parent worksheet continues trying to read the children (perhaps because of the error?). Perhaps a child worksheet could get corrupted if the parent kept trying to read it while the child was being "fixed", corrupting the aforementioned array region. This corruption repeated, in exactly the same region (large array calculation), so maybe some day I will see it again...
Sorry, I can't include my worksheets and data.I've tried to repeat with fake test data and routines, but the simple things appear to check out ok. The timely solution is to avoid includes if they cause any problems for you.
