MS Word - Indexing problem

[saint0]

I don't know you folks and we don't know if you know the answer to this
question, MS Word GURUS. It involves orphan index page numbers
appearing in an MS Word index.

We've tried to remove these entries and their corresponding XE tags, but
the regenerated-updated index still picks up the old page numbers for
the removed index item/entry and continues to display them in the "new"
index.

Is there a fix for this problem that perhaps involves a hidden file such
as a concordance file? Does Word generate a hidden standard index file
that contains a 2-column table for index entries and corresponding page
numbers? If so, where is it so we can KILL it! Or, we would at least
like to modify it to force it to show what we want...

-phillip
(e-mail address removed)
PALO ALTO, CA
USA

 

[garfield-n-odie]

Answered in several other groups. STOP MULTIPOSTING.

 

[Suzanne S. Barnhill]

I think he's going to need a larger clue stick.

 

[saint0]

So, I guess this means that you don't know the answer to this problem? I am
not looking for an imposter who holds a job supposedly helping paid owners of
Microsoft products. I am looking for a Microsoft person who has either coded
the Index function in Word or is very familiar with how it works. The error
I have is embedded in the Word index file table (probably hidden) that
buffers the index item entries and corresponding page numbers. I realize
that since this isn't a "hammer trying to find the proverbial nail type of
problem", your generic "solutions script" may not be able to help me in this
particular instance. Why not escalate this problem to someone at Microsoft
who actually knows the context of the problem instead of embarrassing
yourself and needlessly causing a paying customer trouble here?

 

[garfield-n-odie]

Dear Mr. Full Of Himself Stanford Alumnus:

The solution I gave you is correct. You're only embarrassing yourself
and your fellow Stanford alumni with your behavior in these Microsoft
forums. There is no need to "escalate this problem" because it's not an
error in the Microsoft software; it's a Dumb Shit Operator problem. Way
to go, Stanford.

 

[Margaret Aldis]

Nobody here works for Microsoft - the newsgroups are a peer-to-peer support
network.

Two people (including, IIRC, one of those you've just insulted here) posted
answers to your first post to a newsgroup - you were also asked a question
(whether accepting changes solved the problem) to which you haven't replied.

I had not seen those posts when I replied to your identical question in your
e-mail to me, to which I gave a similar answer. Had I known you'd already
posted I would not have pointed you back at the newsgroups - presumably that
started your bout of multi-posting - but if you had read the link I gave you
you would have found some good advice on 'netiquette'.

I think you might now find it useful to read

http://word.mvps.org/FindHelp/Posting.htm

 

[garfield-n-odie]

Dear Mr. Full Of Himself Stanford Alumnus:

The solution I gave you is correct. You're only embarrassing yourself
and your fellow Stanford alumni with your behavior in these Microsoft
forums. There is no need to "escalate this problem" because it's not an
error in the Microsoft software; it's simply a DSO problem. Way to go,
Stanford.

 

[Suzanne S. Barnhill]

If you are a "paying customer" (that is, you have paid for a support
contract of some sort), then you can use the managed newsgroups, where
Microsoft employees are required to answer your posts (but not guaranteed to
have answers) and to badger you until you tell them whether their "solution"
worked for you, or you can open a support incident with Microsoft via phone.
As others have pointed out, these NGs are for peer-to-peer support, and no
one here is from Microsoft, nor is anyone paid.