FIX: Corrupt Memo and General Fields in 16-Bit FoxPro

Last reviewed: October 14, 1997
Article ID: Q107511
2.00 2.50 2.50a MS-DOS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, and 2.5a

SYMPTOMS

In the Standard (16-bit) version of FoxPro for MS-DOS (FOXPRO.EXE), issuing the APPEND MEMO, COPY MEMO, or REPLACE memo1 WITH memo2 command corrupts the memo field. (The information at the end of the file becomes corrupted with ASCII symbols.) This problem, which also occurs in general or picture fields, occurs when the size of the field exceeds 300K.

STATUS

Microsoft has confirmed this to be a problem in FoxPro 2.0, 2.5, and 2.5a for MS-DOS. This problem was corrected in FoxPro 2.5b for MS-DOS.

MORE INFORMATION

Steps to Reproduce Problem

  1. In the Command window, type:

          CREATE TABLE test (xxx M)
          APPEND MEMO xxx from <text filename>
          BROWSE
    

  2. Look at the database and note the contents of the memo field.

  3. Issue the APPEND MEMO command several more times. Note as the APPEND MEMO command is repeated, the memo field will remain intact as long as the *.FPT file remains under 300K.


Additional reference words: FoxDos buglist2.00 buglist2.50 buglist2.50a
fixlist2.50b 2.00 2.50 2.50a large over more than
buglist2.00 buglist2.50 buglist2.50a fixlist2.50b
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory:
Solution Type : kbfix


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.

Last reviewed: October 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.