| Previous | Next |
| hrColumnIndexed | hrColumnNotFound |
hrColumnTooBig
Diagnostic focus
hrColumnTooBig means the value exceeds the maximum length declared or supported for that column type.
This is the legacy Directory Service backup/restore HRESULT form of JET_errColumnTooBig (0xC80005E2).
The key comparison is: hrColumnLong suggests the ordinary-versus-long-value path; this code is the explicit maximum breach. The first useful observation is to compare encoded length with JET_COLUMNDEF.cbMax and account for terminators and multivalue representation. This evidence separates schema definition, row-size accounting, null semantics, multivalue selection, and stale column IDs.
The ESE objects in play
| Diagnostic layer | column schema, row-size accounting, tagged/multivalued storage, and column identifiers |
|---|---|
| Typical API surface | JetAddColumn, JetDeleteColumn, JetSetColumn, JetRetrieveColumn, and JET_COLUMNDEF |
| Code-specific condition | the value exceeds the maximum length declared or supported for that column type |
| First corrective direction | validate lengths before JetSetColumn and select an appropriate long-value schema when necessary |
Fixed, variable, tagged, and long-value columns consume row space differently. Column IDs are metadata scoped to a table and should be refreshed after schema changes.
Evidence that resolves the ambiguity
- the complete row-size contribution from fixed, variable, tagged, and long-value data; associate it with this result rather than with a later generic exception.
- JET_COLUMNDEF fields, flags, code page, maximum length, and column ID origin; associate it with this result rather than with a later generic exception.
- the encoded value length, null/empty state, and itag sequence.
Nearby results that mean something different
hrColumnNotUpdatable | the selected column cannot be changed in the current schema or update mode |
|---|---|
hrInvalidColumnType | the JET_coltyp value or its option combination is unsupported for this column definition |
hrColumnNotFound | the requested column name or ID is absent from the current table schema |
A disciplined correction path
- Freeze the failing request context and record
0xC80005E2, the Jet API name, and the current instance/session ownership. - Apply the targeted fix: validate lengths before JetSetColumn and select an appropriate long-value schema when necessary.
- Before retrying the operation, reconcile column metadata, row layout, and the exact stored value state.
Actions that can hide or worsen the problem
- Do not alter the column schema in place without a migration and rollback plan.
- Do not collapse null, zero-length data, missing value, and tagged-value deletion into one state.
Technical references
Looking for a different code? Search another status or error code.