Kathy,

In the scenario you described, people work with doc file outside both automation and foxpro. In this case it is the user rights policy that allow to change/replace FILES or not. You can protect the document, but you cannot prevent to rename it or replace with another file.

Only what you could do is to protect the document and create in the document an autoopen macro in which you set
oword.CommandBars("Menu Bar").Controls("File").Controls("&Save"),
saveas, save as HTML, copy, etc. enabled properties to .f.

Still they will be able to replace the file in the windows file explorer.


>Yuri,
>
>Thanks for your reply but the info wasn't what I was looking for. A little more background - after the document is created using a template, it is then emailed automatically to our Configuration Management Specialist. She reviews the document and makes any required changes. Then she emails it to our branches for review. What we have had happen though is the branches will open the document and make minor changes to it (e.g., change a drawing revision letter), print it and then route their new 'master' for signature. The end result is that their routed 'master' does not coincide with the 'master' on the server. In our business, we are required to keep both a hard-copy signed master and an electronic master. By preventing the users from changing the form in any way, we are guaranteed that the hard-copy form and the electronic form are identical.
>
>Thanks!
>
>Kathy