> I'm wary due to my dBase experiences. Maybe I shouldn't be so wary, but my approach evolved from my dBase era, finding a string of binary zeroes slashing through my dbf tables after power disruptions.
>
> Currently, I have applications running for about eight years in a bad power environments, with few if any problems related to file corruption.
>
> select * from customers into cursor x
> use in customers
> *...process x...
> use customers
> *...update customers...
> use
> use in x
>
> Essentially I minimize the existence of open tables.
>
> Server loads are never heavy in this small business environment, so I can open and close a table in at least 1/200th of a second, with confidence that data is stored to disk.


Hi Ed,
Yes a good point you raise in your thread... If you do not have the table
open, it will not become corrupted. However, with the stock VFP forms and
the use of a data environment, all tables involved in the form are opened
when the form opens, and only closes when the form is closed. This aspect
adds to the potential of corruption. Again, one can choose to custom code
and open and close tables only when required, however most do not do this.
The point you raise is another way to minimize the potential for corrupted
tables... open perform your operation, write and close.
Pete from the Great White North. (Only in Canada, ay.) Over and Out ...