| Navigation: ISAM File Drivers > TopSpeed Database Driver > More Details >====== TopSpeed File Errors ====== |    |
Here is a list of the TopSpeed file errors returned by FILEERRORCODE , and a brief explanation:
| 231 | trying to append a record when the btree is marked read-only |
| 232 | cannot get btree header when trying to append a record |
| 256 | cannot get btree header when trying to get a record |
| 300 | btree structure corrupt (discovered when deleting a record) |
| 327 | btree structure corrupt (discovered when putting a record) |
| 337 | trying to put a record when the btree is marked read-only |
| 522 | invalid data size found while unpacking record (from disk) |
| 530 | invalid repeat count found while unpacking record (from disk) |
| 706 | btree structure corrupt (discovered when inserting a record) |
| 780 | btree structure corrupt (discovered when removing a record) |
| 824 | btree record size to big (on allocation) |
| 1013 | cannot get btree header (while loading root page) |
| 1043 | cannot get btree header (while packing a record to disk) |
| 1163 | trying to create new record ID when the btree is marked read-only |
| 1164 | cannot get btree header (while allocating new record ID) |
| 1173 | maximum record ID reached on allocation (probably indicating file corruption) |
| 1194 | trying to insert record when the btree is marked read-only |
| 1203 | trying to remove record when the btree is marked read-only |
| 1364 | btree structure corrupt (discovered while splitting a page) |
| 1477 | btree page size (from header) does not match size stored on disk |
| 1602 | btree unpacked page size (from header) does not match size loaded from disk |
| 1659 | btree page size increased after packing |
| 1678 | btree page size larger than maximum allowed |
| 1735 | btree header corrupt (discovered when trying to calculate disk file size) |
| 1781 | btree structure corrupt (discovered while shifting btree pages up) |
| 1891 | btree structure corrupt (discovered while moving btree pages) |
| 1894 | btree structure corrupt invalid page parent level (discovered while moving btree pages) |
| 2172 | reading of btree page from disk failed |
| 2183 | too many files logged out |
| 2272 | encryption block invalid size (discovered when reading page from disk) |
| 2277 | ReadFile Win32 API function failed (when reading page from disk) |
| 2286 | encryption block invalid size (discovered when writing a page to disk) |
| 2328 | invalid internal btree locking mode (on lock) |
| 2352 | invalid internal btree locking mode (on unlock) |
| 2341 | SetFilePointer Win32 API function failed (when reading page from disk) |
Using the Recovery Utility Interactively
1.Start the utility by DOUBLE-CLICKING on the TopSpeed Database Recovery Utility Icon In the Clarion Program Group.
The TopSpeed Database Recovery Utility dialog appears. The utility consists of two wizard dialogs.
2.In the Source (file to recover) section, specify the file name or press the Browse button to select it from a standard file open dialog.
3.If the file has a password, type it in the Password entry box.
If the database file contains multiple tables (data files), each table must have the same password.
4.Optionally, in the Destination (result file) section, specify the file name for the target file or press the Browse button to select it from a standard file open dialog.
By default the .TPR extension is added to the source file name. This parameter is optional. If omitted, the original (source file) is overwritten and a backup file is created. The source file is renamed to filename.TPx, where x is automatically incremented from 1 to 9 each time a new file is created. If all nine numbers are used, any subsequent files created are given the extension .TP$ and are overwritten.
5.If the result file is to have a different password, type it in the Password entry box. If omitted, the password is removed.
6.Press the Next button.
The second wizard dialog for the TopSpeed Database Recovery Utility appears.
7.Optionally, specify the Example File file name or press the Browse button to select it from a standard file open dialog.
The utility uses the Example File to determine table layouts and key definitions in the event those areas of the source file are damaged. The default extension is .TPE, but if you choose, you may use any valid DOS extension
We recommend shipping an example file when you deploy your application. This improves data recovery from a damaged file.
8.If the example file has a password, type it in the Password entry box.
9.If you want the utility to rebuild Keys, check the Build Keys box.
If omitted, the keys are rebuilt by the original application when it attempts to open it.
10.If you want to use the Header Information in the source file, check the Use Header box.
Using Header Information optimizes the utility's performance, but should not be used if the file header is corrupt. If omitted, the utility searches the entire data file and restores all undamaged pages.
11.If the application uses a Locale (.ENV) File for an alternate collating sequence, specify the .ENV file or press the Browse button to select it from a standard file open dialog.
12.If the file is using the OEM attribute to control the collating sequence, Check the Use OEM box.
This enables the OEMTOANSI and ANSITOOEM conversion.
13.Press the Start button to begin the recovery process.
If the utility does not find any errors, a message appears informing you that “No Errors Detected in <;fliename.ext>” and asks if you want to continue with recovery.