RE: [DUG]: Paradox Corrupt File

2000-05-09 Thread Dennis Chuah


Turn off write behind caching in NT and 95/98, or move to a client/server
database :).

Regards,
Dennis.

 -Original Message-
 I get the same thing with one of my clients (app written in BCB4), all
 of their machines are NT4 Workstation.
 I have attributed it to the following:

   a) main data file is over 100MB
   even though this isn't meant to be a problem
   b) slow network
   c) not all machines have BDE configured optimally.

 As for the third part, I have configured the BDE on a few of the
 machines to increase the number of file handles, buffer
 sizes, etc., and
 this seems to have improved their performance.  I'm not convinced that
 it will solve the index corruption problems.

 My guess is that it is the combination of a) and b) above
 that cause the
 problem.
 As yet I haven't found a way around this.

 Regards,

 Bevan

  HI All,
  I have a Delphi 3 App deployed using Paradox Database.
 
  We always run into Corrupt file problems the message that
 usually comes up
  is "Corrupt File - Other than header Filename.db".
  I use Borland's "DTutil32" to fix the problem and that
 usually fixes it.
  Sometimes I have to remove the indexes from the database
 tables and then
  recreate them and that also fixes the problem.
 
  Just to tell you a little bit about the working environment
 in which the
  Delphi programs are running. What we do is transfer Paradox
 database files
  from another office and then copy them into our current
 database sometimes
  this process works ok but sometimes it gives me the Corrupt
 file error.
 
  But my actual problem is that I get this error message
 every other day and I
  was wondering if any of you know the reason for this and a
 solution if there
  is any?
 
  Thanks in Advance,
 
  Mohsin
 
 
 --
 --
Name: winmail.dat
 winmail.datType: PLAYER File (application/x-pn-mpg)
Encoding: base64

 --
 Bevan Edwards mailto:[EMAIL PROTECTED]
 Achieve Software Limited  http://www.achieve.co.nz
 Phone:(64-9) 444-4210 ICQ: 732011
 Fax:  (64-9) 444-4201
 Mobile:   (64-21) 979-603
 --
 -
 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



Re: [DUG]: Paradox - Corrupt file

1999-03-02 Thread Laurence Bevan

Mark,

Paradox is famous for corrupt files. I have found over the years that it is
generally an index problem caused by users not shutting programs down
properly or Windows crashing etc. There are various things you can do to
minimise it but I haven't used Paradox since Delphi 2 so maybe others can
give you some tips for later Paradox versions.

A pack/repair utility (quite a few are available) is almost essential to
distribute with your application. This way the user can fix it themselves
(doesn't look good from a user perspective, however they get used to it).

Laurence Bevan


---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
  Website: http://www.delphi.org.nz



Re: [DUG]: Paradox - Corrupt file / Databases

1999-03-02 Thread Greg Nixon

Borland have a sample app with source that uses the TTUtility and I never
found a case where it hasn't fixed it. As someone else said you need the
correct TTutility.dll for the BDE version your user has. I have build it
into my apps like I used to do with VB and Access (compress and repair) many
years ago, and tell users to run it on a regular bases to keep there
database. If you can't find the source let me know, but have a look under
the BDE file area.

And while everyone is on the subject of databases I personally find MS SQL
Server great most of the time (except when it goes a-wall and uses up 100%
of the resources and leaves you with little choice but to reboot the
server). When I changed to delphi 1 from VB I missed Access I found paradox
a bit incomplete but it was free so I adjusted. We did one project with IB
back in delphi 1 and yeah the interfaces were pretty horrible then. We have
now been using MS SQL for the past 3 years and found it pretty good overall.
I still use paradox for small projects and use MS SQL for large 1 - 2 Gig
databases. We have only just started using SQL 7 and found quite a few
problems (Mainly because we drived in and installed it on site without
thashing it first). The new ISQLW (Query Anal) is horrible and they must
have used different programmers on this version. It would be nice if they
extended the SQL language to allow you to write your own functions you could
use within a query (eg. like GetDate()).


-Original Message-
From: Mark Howard [EMAIL PROTECTED]
To: Multiple recipients of list delphi [EMAIL PROTECTED]
Date: Tuesday, 2 March 1999 23:00
Subject: [DUG]: Paradox - Corrupt file


Hi all
Novice question
Have a Delphi 3 app deployed using Paradox database.

User today reported message saying  "Corrupt File - other than header
FileName.DB"

Can you people who are doing this stuff every day tell me what you do in
this situation.  What is the immediate fix, if there is one - other than
backup?  Is it likely to be caused by a design fault or is it "just one
of those things".  Having occurred once,  does that mean it is likely to
occurr again?

---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
  Website: http://www.delphi.org.nz



RE: [DUG]: Paradox - Corrupt file

1999-03-02 Thread Dennis Chuah


Mark,

Download TUtility from Borland (Inprise, whatever) and run it against your
files.  I would advise that you do a verify before fixing.  I have found
that while this utility fixes the problem, it can cause records to be "lost"
from the database.  It is best to restore from backups.  This is
particularly important if you get "Blob has been modified" problems.

HTH.

Dennis.

 Hi all
 Novice question
 Have a Delphi 3 app deployed using Paradox database.

 User today reported message saying  "Corrupt File - other than header
 FileName.DB"

 Can you people who are doing this stuff every day tell me what you do in
 this situation.  What is the immediate fix, if there is one - other than
 backup?  Is it likely to be caused by a design fault or is it "just one
 of those things".  Having occurred once,  does that mean it is likely to
 occurr again?

 In this case we were able to go back to a very recent backup - but not
 everyone is as well organised.

 Any and all wisdom will be appreciated.


---
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
  Website: http://www.delphi.org.nz