Thread View: comp.databases.xbase.misc
3 messages
3 total messages
Started by Tom Metro
Thu, 22 Jun 1995 00:00
xbase file integrity checker/fixer
Author: Tom Metro
Date: Thu, 22 Jun 1995 00:00
Date: Thu, 22 Jun 1995 00:00
49 lines
3070 bytes
3070 bytes
I'm looking for a utility that can scan an xbase file (dBASE IV) to find corrupt records and offer to correct the database. Ideally something that is fairly automated so that it can be ran by inexperienced users, but I'll take pointers to anything. The platform can be either Windows or DOS. I've looked through the cica and SimTel (both DOS and Win3) collections and couldn't find anything. I seem to recall from years ago that either Norton Utilities or PC Tools used to have some db tools, but I don't know if they still do. And just as a point of interest, the reason why I need this tool is to correct for database corruption caused by a system crash. I have an application developed in Visual Basic that uses Q+E Software's (formerly Pioneer) Q+E/VB database VBX (the project was created before VB 3.0, with its built-in db support, was released). The slightest bit of database corruption (i.e. something that causes a date field to no longer look like a date) will cause Q+E/VB to return an error and give up on the current operation, so I can't modify my application to handle the corruption in a more graceful way. I have my doubts about Q+E/VB's robustness. The database files can be corrupted even when it is not performing active database I/O. Simply a system reset before the databases have been closed can be a problem. I have SmartDrive's write caching turned off on the systems running the application, but it appears that Q+E/VB is caching some of the data itself. I currently accomplish "fixing" a database file by loading it into the Q+E database editor (bundled with Excel), resaving the file, and rebuilding the index. Sometimes that isn't sufficient as the Q+E database editor will read/write invalid date (and other) formats, while my application can't, so I have to hunt down records containing the garbage and manually delete them. Possibly I could write my own fixup utility in VB 3.0, but I suspect its db interface is not low level enough to allow dealing with corrupt records, as is the case with Q+E/VB. Hopefully the application will be rewritten using VB 3.0 database support, or better yet, in Delphi. In the mean time, I need something to clean up the mess after a system crash. Follow-ups directed to me via email. Write if you want me to post a summary. Thanks, -Tom -- Tom Metro tmetro@lynx.neu.edu Venture Logic tmetro@vl.com Newton, MA, USA
Re: xbase file integrity checker/fixer
Author: Tom Metro
Date: Sun, 25 Jun 1995 00:00
Date: Sun, 25 Jun 1995 00:00
38 lines
1998 bytes
1998 bytes
I asked:
> I'm looking for a utility that can scan an xbase file (dBASE IV) to find
> corrupt records and offer to correct the database.
And here is the only reply I received:
MR RICHARD D SMITH <HGHW60A@prodigy.com> writes:
> I went crazy myself a few years ago with a similar problem. I got a
> DOS based utility called "DBFCLEAN.EXE" from...Borland...
>
> It does a real good job of cleaning up databases after a network
> crash! You may lose some information, but the invalid data causing
> your headaches will be corrected/removed.
>
> You may be able to find it on Borland's BBS.
Yes. It was on their BBS (408) 431-5096.
Go to the "dBASE" conference, select Files, select the "dBASE IV
files" area, and scan the listing until you find:
DBFCLEAN.ZIP 18,089 03/18/92 | Helps clean out corruption in .dbf
Dwnlds: 1,024 DL Time 00:00:12 | files
It was the most popular download :-)
Also, checking at the local computer store I found that the DOS version
of Central Point's PC Tools claims that it has file fixers for database
files. I would assume that dBASE files are covered. Neither the Windows
version of PC Tools or any version of Norton Utilities had "file fixers"
as a listed feature.
-Tom
--
Tom Metro tmetro@lynx.neu.edu
Venture Logic tmetro@vl.com
Newton, MA, USA
Re: xbase file integrity checker/fixer
Author: rduvuru
Date: Thu, 29 Jun 1995 00:00
Date: Thu, 29 Jun 1995 00:00
11 lines
824 bytes
824 bytes
Please try the following: 1. Copy corrupted file to a temp file : copy x.dbf - temp.dbf. 2. Zap temp.dbf using dbase. 3. Append all from x.dbf to temp.dbf. 4. Rename x.dbf to xold.dbf. 5. Rename temp.dbf to x.dbf. Has worked for me in the past. Hope it works for you. Good Luck.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads