The reason I give for this is I have an application that was written with
turbo pascal that I still maintain today that was written with the paradox
engine. When I converted it a cross to delphi it retained the reindexing on
startup, as I do with my current applications. The start up is slightly
slower for the first user, but subsequent users don't reindex so they are
slightly quicker. In the 14 years these aps have been kicking around this
year was the first time I actualy lost data from a table was this year.
This occured when a user turned an NT box off while a table was having
records appended in the middle of a production run. (I missed a 'flush
buffers' in my code after each append)
The main reason I found early on for the table to becoming corrupted is
that the index gets corrupted and the engine starts reading and writing to
the incorrect record. If this carries on in a short period a lot of data is
lost.
The applications I write are in manufacturing envionments with real time
weighing and labeling of product on mixed product lines. If a product is
incorrectly label ( because the product data base was corrupt ) it can lead
to large damages claims ($10,000 min per occurance) therfore it is
important to get it right.
Data is also collected for production anlaysis and inventory perposes so
once again this has to be correct or the inventory will not correct reflect
the warehouse stock.
I hope this gives you an understanding why I personally always reindex
local/shared tables at startup. In the last 6 months I have been coming to
grips with the vagaries of MSSQL 6.5 ( :-( ) with its record locking
problems and network connections dying during updates. I am glad I still
keep copies of my data in local tables for when we have had to rebuild the
server.
Maurice Butler
-----Original Message-----
From: INTERNET:[EMAIL PROTECTED]
Sent: Thursday, 4 March 1999 22:59
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Re: Paradox - Corrupt file / Databases
From: Mark Howard <[EMAIL PROTECTED]>
Hi guys
Thanks for all the replie ti question over the last few days. They are all
printed and will be read carefully when I get time.
On this suggestion below. Would it be considered to be a reasonable
practice
then,. on starting the program, to remove all indexes and re-index, as a
matter
of course? Or would that be a bad idea for some other reasons? I guess if
you
are going to do this you need to make sure that no other copies of the
programme are running on the network. I wouldn't know how to go about
this.
Mark
Maurice Butler wrote:
> Hi,
> If you drop all your indexes, then reindex all databases if you can get
> exclusive access (i.e first user for day) the you will avoid most
problems.
> If the users have a problem they all shutdown. then one restarts and
checks
> if there are still problems then the rest startup.
>
> Maurice
>
> -----Original Message-----
> From: INTERNET:[EMAIL PROTECTED]
> Sent: Tuesday, 2 March 1999 23:51
> To: Multiple recipients of list delphi
> Subject: [DUG]: Re: Paradox - Corrupt file / Databases
>
> If an index file is corrupt then a "techo" way of fixing the problem is:
>
> 1) delete the index file
>
> 2) run up the database administrator
>
> 3) re-index
>
> regards tony goodrich
>
>
---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
