>>>
>>>Yes.
>>>Someone turns off workstation without proper shutdown.
>>
>>I have often heard the above explanation for the index corruption. But I am wondering, if a table is open by the application but the application is idle, would it still corrupt an index? And why?
>
>Any indexed field may have been updated but the updated DBF and/or CDX (the .cdx file may be updated "later" for all I know) records are still in the OS cache and have not been transferred to the real table.
>Keep in mind that that FLUSH without the new VFP9 parameter simply tells the OS that the application is finished with the record. It does NOT ensure that the record is immediately written to the actual table.
>Depending on how VFP handles .CDX files it could be even worse for them.
>
>That's one theory.
I didn't know about the new parameter FLUSH has in VFP 9. I will look it up. It seems to me that forcing the application to write the data to the .dbf and .cdx table should minimize corruption a great deal. Because it seems to me that if the data is physically written to the .dbf and .cdx, turning off a pc should have no effect on the index or table corruption.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
