For scenario #1 you could save your original document as a Word template (*.DOT), that way when you create documents with it they will be saved as .doc preventing the change of the original template. Should be easy enough.

For #2 you could protect the document with a password and only allow read-only access to it. This setup could get complex in code so I'll let you do the research in the help file.

The other option is to show the word document in a an OLE Container control on a VFP form, from there you should be able to expose only the functionality you want.

HTH

>OK,
>
>I put the last request in the wrong area. I have a piece of code that Cetin had sent to someone concerning mailmerge
>I use it to start word allowing the end user to edit filename passed in. Works great except I need to insure end user
>can not rename the file 1st scenario and Can not access the save or saveas buttons 2 scenario so we can control
>the name of the file user is working on. Thought adding command
>
>oWord = GetObject("","word.basic")
>
>With oWord
> .FileNew(myFile)
> .appShow
>*!* Allow user to edit it and then to save it
>EndWith
>*!* Use something like this
> .SaveAs(myFile,".doc")
>*!* or this...
> .Save(myFile,".doc")
> .SaveAs = 0 && False no dialog
>
>I get no errors but the saveas and save dialogs always comes up and allows me to do anything...
>Please Help and thanks in advance...Not Cetin's problem this is my problem not his code failing.
>
>Do it Right! Not Over...
>Cecil