>This is a network issue, not a FoxPro issue. I raised this question myself on this board a couple of years ago and got the same suggestions, which I tried, and none of them corrected the problem. Once I got my network people the list of what I HAD tried, they finally accepted that I had tried everything programmatically that I could and THEY got to looking at it. The best that they could come up with is that the 'unlock' command that the network sends gets dropped (for whatever reason), particularly when the network was overloaded (or just heavily loaded). This could also explain your 'File not found' errors.


Dorris,

Thanks for the confirmation. Yes, I basically came to the same conclusion. Do you still have this problem? Were your Network Administrators able to make anything about it? I can not always answer the users: "It's a Network problem, sorry, nothing could be done from my part" (this is similar to that I'm telling now to users if this problem occurs)
>
>
>>
>>As far as I know, the reprocess setting is left default (e.g. 0). My colleague and I both tried to convince our other colleague, who is in charge of classes changes, what this setting is very important and should not be left unchanged. We both failed in this...
>>
>>Anyway, this particular problem seems to be a Network problem and not related to this setting...
>>
>>We're using Novell Network at work. I also raised another similar issue in another thread. Sometimes without any apparent reason the user sees a message: "Record or file is not available." (something like this). I'm positive, that there are no other users, which open this particular file at this moment...
>>
>>I'm not sure, what should I do at this point as a programmer...