How Bomb Proof is HFSQL C/S ? (15 replies)

Hi,
The last couple of years we have moved many of our users from applications developed with:
Clarion (6x) and Btrieve to WinDev (20 or 21) apps and HFSQL C/S.
Here is what we have found:
1. Performance and Program versatility -> Winner is HFSQL C/S
2. "Bomb Proof" -> Winner is Btrieve (C/S or Workgroup)

Under certain conditions, various HFSQL C/S files can GET corrupted.
We have found that the files that are usually corrupted are the files inside the BDD\__TRS directory of the C/S Engine.
These are the files supporting Transactions and when they get corrupted everything is a mess.

When does this happen?
Usually when the server has a power failure or something like that ...
Of course, we understand that a power failure is not something that should NORMALLY happen in an installation, but it will happen at some time - especially in small installations.

What helps?
Turning off the Hard disk cache - but NOT always.

Question?
Anything out there, as bomb-proof as Btrieve, that plays well with WINDEV?

Regards
Steven Sitas