One other thing besides what was mentioned is to re-code your application so that the tables are closed at all times unless they are being updated. I recently did this in a corporate LAN environment so I could update the tables in the background while others had the application open. Upon application start, I open the tables as readonly, and create a local cursor to work with, then close the tables. This case there is only one daily event to update the tables and this may not be approrpiate in all cases. but a variant may meet your need and prevent table corruption upon power loss.

HTH