When this occurs to me, I've got a bad file, perhaps a bad hard drive.

run checkdisk, or the equivalent on the workstation and the server, if VFP is on a server.

Bad memo fields too, can be a problem - open the project and use the new "check memo field" command.

Craig

>Terry,
>It sounds like a clasic memory leak problem. Keep and eye on the memory usage in the task manager for that application.
>
>Einar
>
>>>Terry;
>>>
>>>I have been using VFP since version 3 beta and have not had that experience. However I have a few friends who have and this leads to a few questions:
>>>
>>>1. Where is VFP located – local or server?
>>>
>>>2. If it is on a server, which network is in use? (Novell was a pain for some)
>>>
>>>3. Are you using a product like Visual SourceSafe? (This was the most common problem)
>>>
>>>4. How about anti virus products?
>>>
>>>5. Memory leak?
>>>
>>>Tom
>>
>>Hi Tom,
>>
>>Funny, I've just written a message to you!
>>
>>1. Local
>>2. n/a
>>3. No
>>4. Yes, Norton's lurking but he only wakes up when there's file transfernce doesn't he? This problem often happens when VFP is the only app working and the pc is essentially idle.
>>5. Not sure what this means - never come across the expression other than on the UT
>>
>>But as I said, I've had this problemette on a variety of m/cs since 1995. I'd just put it down to the vagaries of VFP but now, with the world of VFP expertise and experience at my fingertips, I thought I'd see if I was alone in this phenomenon.
>>
>>Cheers
>>
>>Terry
>>
>>What has been your friends' problem then?