>>>>Often, while I'm working on a form in a project (I'm the only VFP developer here), when I'm ready to save the form, VFP complains that the file is Read-Only, so I cannot save it. To get around it, I SAVE AS - TEMP, and then SAVE AS - the original file name. It appears VFP lets go of the lock when I do the save under another file name.
>>>>
>>>>I'm using VFP 5.0 on a Novell 4.10 server.
>>>>
>>>>Have others encountered this?
>>>
>>>Yes, Happens alot and have not found the problem yet. I have move all dev to local drive and then have to remember to copy up to server.
>>>
>>>Jeff
>>
>>If either of you find the reason (or better yet, a solution) for this, I would like to know, as this is the cause for a bunch of hassle at one of my clients' sites.
>
>FWIW, I was having this problem frequently, but it disappeared after I deleted my FoxUser DBF.

There are three programmers at this site, and none of us are able to reliably edit a form that is stored on the network. We have attributed it (so far) to some network anomoly. I will try killing my Foxuser.dbf tomorrow. Thanks