Hi, Dragan.
> Where did you dig this out?
To my large regret, itself has come across. There was a sea of blood, as together with indexes are broken and appropriate relations.
> What could be the possible reason - one form involved in transaction and other not, or what?
Here it should be necessary executed 5 conditions:
1. The form should contain the table with the established flag ReadOnly.
2. This form should be started by first. (First should opens a file with access on reading).
3. Other form should contain the table with established buffering.
4. Updating the table should be made in a Transaction.
5. In the forms should be different Data Session.
To bypass a problem I has decided to break the first condition.
To understand it it was heavy, as there was no clearness, for what reason crash indexes in the network application. To be sure, that there are no other ways to destroy indexes in Fox; - (.
Can there were such?