TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Word SEQ field question From:"Bergerson, Carl A" <Carl -dot- Bergerson -at- UNISYS -dot- COM> Date:Mon, 2 Mar 1998 16:45:26 -0500
Beth,
You didn't mention what version of Word you are using.
With Word 8, you can use a new field, DocVariable, to do what you want.
With Word 6 and 7, you can use the File, Summary Info screen to save a
few pieces of information (assuming you're not using those items for
their intended purpose <g>), and then put them in your document using a
Document Information field.
HTH.
Carl Bergerson
Mission Viejo
Product Information
carl -dot- bergerson -at- unisys -dot- com
> ----------
> From: Beth Friedman[SMTP:bjf -at- WAVEFRONT -dot- COM]
> Sent: Monday, March 02, 1998 1:27 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Word SEQ field question
>
> In our previous episode, Walter Hanig said:
>
> > Is there a specific reason for using a SEQ field to accomplish the
> > reference? I suggest you select the {SEQ app \r 1 \* Alphabetic}
> > field and define it as a bookmark. Then you can just use {REF
> > bookmarkname} to refer to it. If you have multiple chapters or
> > appendices in the same file, you'll need to define a unique
> > bookmarkname for each chapter number and appendix letter.
>
> I'm having a similar problem, I think. I need to get changing text
> into a header. The usual way would be with a styleref field, but
> there isn't any place that the text that would be referenced is used.
> I was thinking I could create a style in the document that was defined
> as hidden text, and that works. Unfortunately, the text in the
> styleref field shows up as hidden as well, unless I define the
> paragraph in the document as un-hidden, which loses the whole point of
> the exercise.
>
> Any ideas? I don't want to have to start fiddling with ASK fields if
> I don't have to when Styleref is so elegant.
>
> *********************************************************************
> Beth Friedman bjf -at- wavefront -dot- com
>