>>>VFP 8 displays a warning message (file is in use by another) as you attempt to save a program which is currently being viewed (non editable) by another user. This message alerts users that the file is open by another user and will need to be closed prior to saving the newly edited program. Any coding changes to the program file remain intact until other copies of the program are safely closed and the new changes can be saved to the program file.
>>>
>>>Conversely in VFP9
>>>
>>>When attempting to save to a program file which is being viewed by another user(non editable) VFP 9 closes the file without saving changes and displays the message "File access is Denied". We've spent hours recoding program files due to this VFP 9 Bug.
>>>
>>>Please include a resolution for this in VFP service pack 1
>>
>>I have never noticed this myself, so I can not comment on if this is a bug or not. But the first thought that strikes me, is "why the heck doesn't this guy use version control?". As for a resolution: not tried, but what about Save as a temp name?
>
>Hey Tore
>
>This is the kind of thing that makes me recommend not having multiple procedures and functions in one .PRG. Very little chance of this "bug" happening then.

What I do, is always work against local .prg files, and then use Beyond Compare to copy the modified files to the file server.