In previous versions of the Jet Data Manager the fields on a history-enabled table could be either a part of the natural key, a type I or type II field. In the new release we have added support for type 0 fields. Type 0 fields are basically ignored by the Jet Data Manager - they are inserted together with the rest of the record when it is created (either on the initial load or on a type II change) but they do not trigger an update.
Type 0 fields give you more flexibility for your history-enabled tables. For instance you might have fields with values that are calculated by custom code inside or outside the Jet Data Manager.