H
hrlngrv
Thought I'd share this one. Someone somewhere in the company I work for
designed a database solution for an asset-liability matching system.
The design used separate tables of contract numbers for generating
assets and liabilities. At year-end, one of my unit's contract numbers
was in one table but not the other. Result: a > US$9 million screw-up
on a single account.
Maybe spreadsheet errors are more common than database errors, but
database errors tend to cost more in the long run.
designed a database solution for an asset-liability matching system.
The design used separate tables of contract numbers for generating
assets and liabilities. At year-end, one of my unit's contract numbers
was in one table but not the other. Result: a > US$9 million screw-up
on a single account.
Maybe spreadsheet errors are more common than database errors, but
database errors tend to cost more in the long run.