Hi John,

I honestly don't know.

But can you please clarify. . . you say below "The result is, yes, it may cause illegal operation while access the index corrupted table.". Does this mean that the index BECAME CORRUPTED by the operation or that the index was ALREADY corrupted and the accessing PC failed because of that?

Someone in that thread I pointed you to long ago said that they addressed the problem by immediately RE-READING the written data and taking steps if not obtained. I don't remember the details, but I think it was well described. MAYBE that is worth trying.

It is also worth pointing out, now that you have tried with 3-4 workstations only, that NETWORK cabling/setup/NICs could all be suspects too, ESPECIALLY since I remember you saying that you have NO problems in another shop with only 3-4 PCs attached.

I wish I could be more helpful.

By the way, I still don't see how disabling write cache on PCs can cause failures. Maybe if done while something is using it, but surely not if the system is quiet at the time.


>Hi,
>I haved limited 3-4 workstation to access the "server" in my client site. And 1 workstation may/may not access the "server" to view current sales value time to time. Other than that, this pc will not access the database at "server".
>
>The result is, yes, it may cause illegal operation while access the index corrupted table.
>
>So, what do you think I should do in next step? use FLOCK/RLOCK instead of TRANSACTION?
>
>Pls advise
>
>Thank you