Uniface invoice archive uses SHA-256 checksums to detect file changes, with limits
The author extends a Uniface 10 customer app with an archive that stores every issued invoice and credit note of a year as an HTML file. Each file's SHA-256 checksum is saved in an ARCHIVE_ENTRY table, enforced to one row per document by a unique index. A follow-up operation later recomputes the checksums and reports each file as OK, MISSING, or CHANGED in an index file. The archive reuses the same rendering operation used for printing, and cancelled invoices are archived along with their reversing credit notes. The article also examines what a checksum can and cannot prove about the archived records, which the author says is weaker than it first appears.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in