This happened to me a couple of years ago. I researched and researched and tried everything I could think of in VFP. Nothing fixed it. It only happened in the afternoons. We finally found out that our system was actually overheating and that was causing the strange behavior. As soon as we replace the processor/fans/etc and increased the cooling in the room itself, all of the problems went away! None of the hardware monitors showed any heating/cooling problems during the entire time either. Don't know if it helps, but it solved my problem back then.
One more thing, what OS is this on? If it is Novell, make sure you purge your deleted files periodically on the server-that can cause problems over time too. Any other OS get rid of any left over temporary files created that may be hanging around over time in both VFP and the OS. Just some thoughts on things I ran into over the years.
Tracy

>Paul -
>
>This could be happening. The errors seem to have local views involved. Do you know which page/chapter/book this was in? I'm looking at:
>

>The Fundamentals: Building Visual Studio Applications on a Visual Foxpro 6.0 Foundation
>

>
>by Wil Hentzen.
>
>Is this the book you're referring to?
>
>- George
>
>>By any chance do you have views defined in your DBC and all users have access to the same DBC? If so, I recall reading one of the Hentzenwerke books--I don't remember which one--that all views should be stored in a local DBC. There seems to be an issue that VFP will lock the view for a short time; hence, user conflict with two or more user opening a the same view at the same time.
>>
>>This one problem maybe the cause of all your other errors that you are getting.
>>
>>HTH,
>>
>>--Paul