FIX: "Conversion Cancelled. Adjust Memo BLOCKSIZE"

Last reviewed: October 20, 1997
Article ID: Q114146
2.60    | 2.60
WINDOWS | MS-DOS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.6
  • Microsoft FoxPro for MS-DOS, version 2.6

SYMPTOMS

When you attempt to open a database created in dBASE IV and convert the memo file to the FoxPro format, the following error message is displayed, and the database is not opened:

   Conversion cancelled.  Adjust memo BLOCKSIZE.

CAUSE

The memo file header is less than 512 bytes. dBASE makes the memo file header equal to the BLOCKSIZE when the memo blocksize is less than 512 bytes. However, FoxPro always uses a header of 512 bytes.

RESOLUTION

To resolve the problem, the memo blocksize in dBASE needs to be set to 512 bytes or greater. To do this:

  1. Start dBASE IV.

  2. Issue the following commands at the dot prompt:

          USE mydata
    
              ** where "mydata" is the name of the database
    
          SET BLOCKSIZE TO 1
              ** this can be any number between 1 and 32
    
          COPY TO newdata WITH PRODUCTION
              ** WITH PRODUCTION copies associated MDX with the database
    
    
The new table ("newdata" in this example) has a blocksize that can FoxPro can convert.

STATUS

Microsoft has confirmed this to be a problem in FoxPro 2.6 for Windows and FoxPro 2.6 for MS-DOS. This problem was corrected in FoxPro 2.6a for Windows and in FoxPro 2.6a for MS-DOS.


Additional reference words: FoxDos FoxWin 2.60 buglist2.60 dbt mdx
fixlist2.60a
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxinteropDbase
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 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.