DOC: Additional Jet Database Record Size Information

ID: Q198660

The information in this article applies to:

Microsoft Visual Basic Professional and Enterprise Editions for Windows, versions 4.0, 5.0, 6.0
Microsoft Access versions 7.0, 97

SUMMARY

Because Microsoft Jet allows for variable length fields, you may occasionally receive DAO error 3047:

"Record Too Large"

This occurs if the physical storage requirements of a record exceeds the amount of free space available in a data page (about 2000 bytes).

Appendix A of the Microsoft Jet Database Engine Programmer's Guide provides a list of factors you must take into account when estimating the size of a record in a Microsoft Jet database (MDB file). The book omits some information regarding MEMO and OLE fields.

MORE INFORMATION

The Microsoft Jet Database Engine Programmer's Guide, Appendix A, documents that Microsoft Jet stores MEMO and OLE fields on separate pages (Long Value pages) from the rest of the record. And that for every non-NULL MEMO or OLE field, there is a 12-byte overhead in the main record that points to the location of the start of the Long Value page chain.

Appendix A, however, does not document that Microsoft Jet 3.5 and earlier will attempt to store the MEMO or OLE value in the main record if the size of the data is less than or equal to 32 bytes. This results in faster lookup of these values and does not incur an additional 2K storage overhead, but does retain the 12-byte overhead. If the record is very large, (approaching 2000 bytes for example, the maximum record size), the MEMO and OLE fields will be stored in a Long Value page even if 32 bytes or less.

Additional query words:

Keywords : kbdocfix kbAccess kbDatabase kbJET kbODBC kbVBp400 kbVBp500 kbVBp600
Version : WINDOWS:4.0,5.0,6.0,7.0,97
Platform : WINDOWS
Issue type : kbinfo