Windev 25 Dump Verified Now
If you only want to check the integrity of a dump file without loading it into the database:
// Verify dump header and blocks
oDump is DumpFile
oDump.File = "D:\Backups\sales_dump.WDD"
IF oDump.Verify() = True THEN
Info("Dump verified. Record count: ", oDump.TotalRecords)
Info("Checksum: ", oDump.Checksum)
ELSE
Error("Dump corrupted at block: ", oDump.CorruptedBlockIndex)
END
Note: The DumpFile class is available in WINDEV 25 Update 2 and later. windev 25 dump verified
PC SOFT provides the HF7 Control Center (free utility). Load your .WDD dump and click "Verify Dump" . The tool will: If you only want to check the integrity
Cause: Another process modified the source during the dump.
Solution: Always perform verified dumps in exclusive mode: Note: The DumpFile class is available in WINDEV
HOpen("MyTable", hOReadWrite + hOExclusive)
HDumpFile(...)
HClose("MyTable")
lmv to list modules, versions, timestamps.~* e !locks, !stacks), check for mutex/IO waits, and thread stuck in message loop or synchronous call.The term "Verified" attached to a dump indicates a successful analysis of that crash data. In the context of WinDev 25, this usually relates to one of two scenarios:
WINDEV 25 operates primarily with the Hyper File 5 database. Unlike client-server SQL databases that rely on transaction logs, HF5 is a file-based system. While extremely fast for standalone and client-server setups (via HFSQL), it is susceptible to:
A standard backup copies the raw .FIC files. A dump, however, reads the logical content of the database and writes it to a new, clean file (usually .WDD or a text-based .TXT or .XML). The "verified" flag means that after writing the dump, WINDEV 25 performs a line-by-line or record-by-record comparison between the source and the dump, using a CRC (Cyclic Redundancy Check) or internal hash function to ensure 100% fidelity.