>Hi all,
>
>A question from my boss on using a Database container:
>
>"What is the potential impact to the dbc if a workstation powers down with it [the DBC] open?"
>
>Thanks for the information...
>
>
>Robert
The program on the end-user's machine doesn't write any changes to the DBC, so there should be no problem.
The individual tables and indices are a totally different situation.
You should issue FLUSH after saving changes (with TableUpdate()), to minimize corruption.
HTH, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
