1 - you get this too if all field > 64 ko (pb of IsSummary)

2 - In my application iam facing 32k limit issue(Lotus Notes Exception - Field is too large (32K) or View's column & selection formulas are too large). I went to database properties and checked "Limit entries in $UpdatedBy fields" option, it is mentioned as 10 only. Even though iam facing this issue. Please help me how to trace out this problem.
Thanks,
Ragini

3 - In my application iam facing 32k limit issue(Lotus Notes Exception - Field is too large (32K) or View's column & selection formulas are too large). I went to database properties and checked "Limit entries in $UpdatedBy fields" option, it is mentioned as 10 only. Even though iam facing this issue. Please help me how to trace out this problem.
Thanks,
Ragini

4 - even i've receing same error.
Is anybody found a solution for it. Pls suggest

regards
Murali V
murali.v@axa-tech.com

5 -
Can't find a way to run agents or do anything to affected documents.

In my case documents were created by agents. Individual field sizes were not a problem because they were max around 2K but because there were so many fields it was the total document summary caused the issue (as mentioned above the limit is 64K for thew whole document).

I modified the agent to remove the summary flag for all items larger than 1000 bytes when saving/mailing the document and that got rid of the error.

Use item.setSummary (false) in Java/API
Use item.isSummary=False in LotusScript

Incidentally if you copy an item to another document using document.replaceItemValue it will add the summary flag back because it is on in new items by default.

6 - Am an MS Access app pgmr, shocked at the chaos and crudity of Lotus Notes, as an application environment. It may have some "versatility" and "flexibility" lacking in MS Access, but that seems -- in practice -- to translate into absolute slop, with grossly understructured databases and chaotic disorder gradually growing and worsening over time, in a large IT enviroinment. Lotus Notes may have speed and security advantages, but its main security advantage seems to be that it's so damned difficult to get good meaningful data into and out of it that it's not worth the trouble. Who, in their right mind, would want to hack into such a fouled up mess, looking for anything? As a development tool, it reminds me of an early MS-DOS version of dBase or Symphony, with lots of opportunties for you to do things, with precious little warning of how terribly bad everything can get, very quickly, and error messages that are in mumbo-jumbo code reminiscent of Microsoft Windows' infamous blue screen of death. Lotus Notes looks like one gigantic kluge, patched to insanity.

7 - You need to check you document size, it should not exceed the 64kb limit and the individual field limit is 32k.

The solution to this is that need to change the field type to rich text in which u are facing the 32 k ( you can the field by looking into the text of field).

8 - Dear RH, ignotrance is bliss isn't it?

MS Access is a 'personal productivty tool' NOT a corporate IT tool.
It cannot support more than 10 concurrent users in a coherent fashion. Much better to use SQL or something similar, hey how about Lotus Notes??

9 - RH, you aren't even an informed troll.

10 - These errors occur when a particular Text field in the document or the document itself has reached the maximum amount of Summary data that it can hold.
Notes/Domino 6.x and later have the following limits regarding Summary fields: 32k per field, 64k per document.
Relative to memos: The limit for sending to individual names and locally expanded groups is 15k.

1.If the limit is relative to a particular field, workarounds are as follows:
- If the field must be of the Type Summary (allowing it to display in views) then the only workaround is to remove some of the text or place some of the text into another field (it is unlikely that 32k worth of data would be displayed in a view).
- If the field does not need to be displayed in a view then change the Type of the field to Rich Text or Rich Text Lite.
- Relative to memos: Remove names from the recipient fields and send a second memo or create one or more public groups and address the memo to the group(s) instead.

2.If the limit is relative to the total document, workarounds are as follows:
- Change whatever fields that do not need to be displayed in a view to Rich Text or Rich Text Lite.
- If the fields must be displayed in a view then there is no alternative but to break the information up into two documents.