Some months ago I was developing an application for Lotus Notes clients: I wanted to build a dinamic list/table into a Notes document where each row had to show information about a Spare Parts item.
Each row had to contain the following information:
- a spare part code
- a description
- a quantity
- a LotusScript button to process that specific spare part code (let's say something like "add this item/code to the shopping cart"...)
The numbers of items in the Spare Parts list/table could not be a fixed number.
I decide to use DXL = XML for Domino
By the way, using DXL classes you can export/import data document from/to a Notes database, just dealing with text XML files.
Reading the Designer Help db you can find info about LS classes to work with DXL:
NotesDXLexporter and NotesDXLimporter classes.
Everything was fine with that application on Lotus Notes client release 6.5.x ... until we upgraded to release 7.
I suddenly could NOT see anymore the dynamic-sized spare parts list/table into any R7/R8 Lotus Notes client because the DXL importer could NOT load the all DXL file prepared by another LS procedure!
No problems with R6.5.x clients, just with R7 clients users.
I realized I could see the log of the DXL importer class, that is printing the Log property soon after the run-time error.
"Warning: Memory allocation request exceeded 65,000 bytes"
I was not worried by the warning message: "as soon it was not a fatal importer error..."
But I was wrong, in fact the Spare Parts list/table did not show into the document!
After some search I found the following IBM technote # 1255264 :
Message 'Warning: Memory allocation request exceeded 65,000 bytes' importing a DXL file
and I setup DXL_DISABLE_LS_COMPILE=1 var into the Notes.ini.
It just resolved any troubles in Lotus Notes clients R6.5.1, R7 and R8.
See the following PDF document with a sample LS function createSparePartsTable() that take care of building the dynamic Spare Parts list/table using data from the array parameter (2nd parameter) and storing the generated table into a richtext item (body) inside the origdoc parameter (1st parameter).
PDF document: http://www.divshare.com/download/2995732-eb6