Customising header info (Word 2003)

Topic

New Reply

I am going to automate the production of a construction project specification file, in which I need to insert project information in the header and footer of each section. I start with a master file which contains a number of sections (e.g.., 03100 Formwork, 03200 Reinforcing steel, 03300 Concrete, 05100 Structural steel, etc,…).
Each section has its own header with section-specific info, but all headers also contain the same project information: project number and title, and the specification version (e.g., For Tender, or For Construction).
Once the specs are produced with project info in the headers and footers, I need to be able to modify the text of the document for particular requirements for the project.
Once the document is set up, I need to be able to save a copy which will not change, as a record. Then I need to be able to produce the next version from the saved record, for example when I go from the “For Tenders” version to the “For Construction” version.

What would be the best way to set this up ?
I don’t want to use a form, because I don’t want to lock the document.
Does the ASK function require locking the document ? The Help says that the ASK is better than Fillin if I require the information to be inserted in several places, which is my case.

Thanks for any advice.

Reply | Quote

Replies

Neither ASK nor FILLIN require the document to be locked – rather the reverse.

Another option is to set document variables in VBA, and place DocVariable fields in the document that refer to these variables. See post 259,183 for a demo – it employs a userform to set document variables, and the page header contains DocVariable fields that display the value of these variables.

Alternatively, you could use custom document properties and DocProperty fields. Custom document properties can be edited by the user in Document Properties; this can be an advantage or a disadvantage depending on your requirements.

Reply | Quote

Thanks Hans. I have succeeded in setting up the Custom document properties, which suits me fine. I may need to think about future users also, so I may one day change to the user form method as in the demo you mention.

Kevin

Reply | Quote