Robert,

The approach we use is to have the "originating department" (aka document owner) create an Acrobat file from the original every time they issue or release a document. The Acrobat file is not editable - and thus secure from unauthorized changes. The Word document is stored in a different subdirectory with limited access rights.

In the VFP app, we have a document control module that lists document number, revision, date, status (ACTIVE, OBSOLETE or WRITING), originating department and title. There is also a field for the Acrobat filename that has next to it a GETFILE button and a button to launch Acrobat with the current filename. The getfile button, as well as the add, save and cancel buttons are enabled only for the appropriate department.

Its a fairly simple solution but it has worked well for us over the last 6 years (originally an FPW app). We've considered eliminating the Acrobat documents and going with read-only Word automation...but at some point many of these documents will be needed for Web access (MSDS's, etc) so for now we are staying where we are.

HTH,