Microsoft KB Archive/128222

{|
 * width="100%"|

PRB: Memo Field Limits Incorrect in Help System
'Article ID: Q128222

Creation Date: 28-MAR-1995

Revision Date: 19-SEP-1996' The information in this article applies to:


 * Microsoft Access versions 2.0

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

The Microsoft Access version 2.0 Help topics "DataType Property" and "Choosing a Field Data Type" incorrectly state that the maximum size of a Memo field is 64 kylobytes (K) (or 65,535 characters). Appendix A of the version 2.0 User's Guide also gives the wrong value of 64,000 characters on page 708.

RESOLUTION

Microsoft Access limits Memo field storage to 32K. However, you can use the GetChunk and AppendChunk methods in Visual Basic for Applications (or in Access Basic in Microsoft Access 2.0) to store up to 1 gigabyte (the maximum size of a database) of data in a Memo field.

REFERENCES

For more information about the GetChunk and AppendChunk methods, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q103257 TITLE    : INF: Reading, Storing, & Writing Binary Large Objects (BLOBs)
 * }

-

"THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY." '' ©1997 Microsoft Corporation. All rights reserved. Legal Notices.

''

Additional reference words: 2.00

KBCategory: kbusage kbdocerr

KBSubcategory: DcmHlp