Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Binaries » View Thread |
Messages 1 to 4 of 4 total |
DBISam V3 - Error # 12035 Table is not the correct version |
Tue, Apr 15 2008 7:51 PM | Permanent Link |
"Gregory Sebastian" | End user sent me a database with the above problem (table attached). The
table cannot be repaired with the Table.Repair method. Does anyone know that causes this problem ? I don't have a clue. Thanks Gregory Sebastian Attachments: Comments.zip |
Wed, Apr 16 2008 3:18 AM | Permanent Link |
Steve Forbes Team Elevate | Hi Greg,
It appears that the client has somehow overwritten the IDX with the BLB file, if you delete (or rename)the IDX you will be able to open the data file and reconstruct the index. -- Best Regards Steve [Team Elevate] "Gregory Sebastian" <gregorys@nospam-ezysoft-dev.com> wrote in message news:43567D16-1DD9-44FE-AC22-C0AB03713C95@news.elevatesoft.com... > End user sent me a database with the above problem (table attached). The > table cannot be repaired with the Table.Repair method. Does anyone know > that > causes this problem ? I don't have a clue. > > Thanks > Gregory Sebastian > |
Wed, Apr 16 2008 7:18 PM | Permanent Link |
"Gregory Sebastian" | >if you delete (or rename)the IDX you will be able to open the data file and
>reconstruct the index Thanks Steve, that did solve the problem. But I'm not sure if he accidentally overwrote the IDX with the BLB or any other file. I opened the damaged IDX file with Notepad and it looks like any other IDX file but it must be damaged or corrupted somehow. Weird. Thanks again Gregory Sebastian |
Thu, Apr 17 2008 4:03 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Gregory,
<< Thanks Steve, that did solve the problem. But I'm not sure if he accidentally overwrote the IDX with the BLB or any other file. I opened the damaged IDX file with Notepad and it looks like any other IDX file but it must be damaged or corrupted somehow. Weird. >> If the .idx becomes damaged enough that the header has the wrong version number in it, then it will cause this type of issue. And Steve is correct - the remedy is to delete the .idx, re-open the table, and then re-add all of the missing indexes. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Monday, April 29, 2024 at 05:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |