I have a form that is getting big (18K fields at max) and I am running into the 32K problem around 1/3 of that size. I cannot use rich text since the fields are used in math calculations, but I am thinking that I could use computed for display for all the non-entry fields and store values in backend Notes with the IsSummay property off. I can switch the property off of course, but since the fields are in the UI they reset on everysave. Does anyone know if computed fro display are included in the 32K when a save is being done. I know you can find the field in the document properties, but since it is not save it should not matter.
Any other idea’s? I am open to suggestions.
Thanks!
Subject: You can turn IsSummary off on fields not needed for views
Update : I see that you have already considered the information below, but I’ll leave it in for others.
I’d suggest you do your calculations in LotusScript, store the values in non-summary items, and display the values in computed-for-display fields on the form under a different name. Or, you can set the Save-to-disk value of some item to False if you only need them while the form is open.
The Summary area of the document is used by the process that builds the views. So if you have some large fields are will not be needed by views, you can turn off the summary flag for those fields, and they won’t contribute to the 32K limit.
e.g. In the QuerySave event…
doc.GetFirstItem(“XXX”).IsSummary = False
Also, note that items created in Script using the extended syntax ( doc.NewItem = “Summary”) are created with the summary flag on, while items create with the new operator ( set NewItem = New NotesItem ( doc, “NewItem”, “NotSummary” ) have it set to false.