Hi, Nancy.
The brought code, shows only problem and does not contain any working processing. The developed program is a network application, where some independent forms, simultaneously are opened, with Dataenvironment, events, methods, processing and ... =>Private data sessions to me are necessary. I agree, if them to not use, a problem will not be. To bypass this problem there is enough to not execute even one of five conditions. I have decided to refuse flag ReadOnly (though and it is very a pity). I can not refuse from Private data sessions, buffering, of indexes and I do not want to determine the rigid order of start of the forms.
Further. Time at you, Nancy, the same effect, it - bug has turned out? Means, the index file is not updated, if it is already opened in other session with access only on reading. It was extracted by large blood (as together with indexes the relations are broken also). As far as I understand should not be the ways in the Fox-program to crash an index file. Or I am not right?
PS. Can in a rate, VFP 6 these effects occur (program works as)?