This is just a note to anyone who gets the same error reported in this thread.
The issue stems from a Unidata-specific bug (more like a well intended design flaw) with the way the CHANGE() and SWAP() functions handle substitutions of large strings, which is exactly what our NebulaXLite product does to create XML-based spreadsheets. IBM has created a fix which should be in the next release. Big thanks go to Wally Terhune and the IBM team for their efforts on this, as well as to our client (can name himself if he wishes, I'm intimidated by email disclaimers. ;) ) for working closely with Nebula R&D as we created and tested workarounds to get around the issues. Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Latest info on NebulaXLite: remove.pleaseNebula-RnD.com/forum/index.php/board,10.0.html Latest blog entry: PDA GUI for MV - Success remove.pleaseNebula-RnD.com/blog > From: Tony G > I'm running Win/UDPE 7.2 for development. When > running a program with a few hundred K of variables > being tossed around, the connection running the > process will die, sometimes just gasping out this > message: > > Size of memory requested (146157568, 35683 local > pages) is too big! > > The same code (adjusted for platform-specific nuances) > runs without a hitch on in another MV environment. It > looks like Unidata is attempting to pre-allocate > excessive amounts of memory as soon as it sees some > volume of actual usage. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
