Subject: Reserve field question
Check the database properties (last tab) and make sure the value meets your needs especially if someone is writting code to this field (I highly suggest not doint that.) If the field is being modified and being made wider then the date and time (default) then do the math - you will reach a 32K limit quickly on this field.
For your convenience - help:
Any custom code writing to this field woudl be of form:
notesDatabase.LimitRevisions
Limit the size of $Revisions fields
Every document includes a $Revisions field that stores, by default, the date and time of each document editing session. Domino uses this field to resolve replication or save conflicts that occur when two users simultaneously edit the same document on one replica or edit the same document on different replicas between replications.
By default, the $Revisions field stores a history of up to 500 edit sessions, each of which requires 8 bytes of disk space. Over time, $Revisions fields can grow large, taking up disk space and slowing view updates and replication. To conserve disk space and improve database performance, use the Advanced database property “Limit entries in $Revisions fields” to specify the number of entries that the $Revisions field can contain. When the $Revisions field reaches this limit, the oldest entry is removed to make room for the newest entry.
Consider limiting the entries in $Revisions fields on a database with all of the following characteristics:
The database contains many documents.
The database replicates often or has no replicas.
The database contains documents that are not often edited.
A suggested upper limit is 10 entries in the $Revisions field. If you set the limit lower than 10, you run the risk of increased replication or save conflicts.