FIX: Index Doesn't Match Table When Opening dBASE TableLast reviewed: October 20, 1997Article ID: Q114145 |
2.60 | 2.60WINDOWS | MS-DOS kbprg kbfixlist kbbuglist The information in this article applies to:
SYMPTOMSWhen you attempt to use a dBASE IV (version 2.0) database, the following message is displayed:
Index does not match table. Re-create index. CAUSEThe index blocksize in dBASE was set to a size other than 1 or 2 (or 512 bytes) with the SET IBLOCK command. The index blocksize can also be set with the SET BLOCKSIZE command, which sets the blocksize for both memo files and index files.
RESOLUTIONIMPORTANT: Neither of the two methods (described below) to correct this problem will work if the database has one or more memo fields that were converted to FoxPro memo fields before the "Index does not match table" error message was displayed.
Method 1To make the dBASE .MDX file readable by FoxPro, issue the following commands from the dot prompt in dBASE IV:
USE <filename> SET IBLOCK TO 1 COPY TO <newfilename> WITH PRODUCTIONThis will make a new copy of the database and the index file with the correct index blocksize of 1 (512 bytes).
Method 2If dBASE IV is not available, re-create the indexes as follows:
STATUSMicrosoft has confirmed this to be a problem in Microsoft FoxPro for Windows and MS-DOS, version 2.6. This problem was corrected in Microsoft FoxPro for Windows and MS-DOS, version 2.6a.
MORE INFORMATIONThe SET IBLOCK command sets the blocksize for new index files in blocks of 512 bytes. Valid values range from 1 to 63. Any value greater than 2 will cause the problem described above.
Steps to Reproduce Problem
|
Additional reference words: FoxDos FoxWin 2.60 buglist2.60 mdx cdx re-
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |