Hello Paradox users
Here is one example of handling Paradox table maintenance and repair.
The utility DLL supplied by Borland, TUtil32.DLL, (ver 5.??) supplies basic
functionality.
Alec Bergamini of O&A (www.o2a.com) supplies excellent software using
TUtility and his documentation is the best I have seen describing Paradox
features, problems and quirks. Using his DLL allows me to use the
functionality without having to understand the details of TUtil32.DLL. (Why
reinvent ...?) To use Alec's DLL you need a clean copy of your database
files to serve as a reference. This is easily handled by keeping a copy of
your database in a separate directory which is used only as a reference.
I have written a TableFix program which uses Alec's work and requires one
to supply three items: the name of a text file listing the tables of your
active database, and alias' pointing to the working database and the
reference copy of the database. Tablefix can be run to repair all the
Paradox table errors I have seen.
I am happy to give away copies of TableFix to anyone who has purchased
Alec's package. Email me if interested.
The last time I checked the TUtil32 DLL did not correctly handle Paradox
field types of "Formatted Memo". If you are not using "paradox the
development tool" you can bypass these types and use "Memo" for your Rich
Text fields.
Running a program to rebuild indices at the start of a program seems to be
an unwise idea as rebuilding index files correctly usually requires
exclusive use of database files by the repairing program. I would suggest
running a repair program only when necessary.
Regards
>
At 13:43 9/06/2000 +1200, Patrick wrote:
>Quoting Mark Howard <[EMAIL PROTECTED]>:
>
> > Hi
> >
> > My users have had the occaisional problem with Paradox table and
> > or index corruption - normally caused by a power outage or
> > someone running a backup with the databse open.
> >
> > In the past I have been able to fix things most of the time by
> > deleting the index files and then redefining the primary and
> > secondary index's, using the DBD.
> >
> > This hasn't always worked - and hasn't in the current case. What
> > is the best way of dealing with this problem?
>
>Basically you have 3 options:
>
>1. Buy a commercial product like TV which is done by Wade A. From memory it's
>about $300.
>
>2. Use the freebie table repair utility on Borland's web site.
>
>3. Develop your own, preferably using components like the TTUtility component
>set from Out & About www.o2a.com
>
>It may still be of course that the problem that your client has had can't be
>repaired - and that is when backups are important.
>
> >
> > Also, on a similar topic, would it be good, bad or indifferent
> > practice to programatically delete and rebuild the index's each
> > time the application opens, to keep them clean. (Or is that a
> > dumb question?)
>
>I believe some people here do it, like Russell Belding.
>
>
> > Can you repack tables programatically? How?
>
>You can use the TTutility components to do all sorts of things.
>---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
Russell Belding
Belding Computing
http://www.belding.co.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
