Cross-references in a different document

We have used FrameMaker for years (currently Version 7.1). We are in the process of switching to InDesign (CS5).
One current project is a print catalog where I put each section in a different document. One of the sections is a list of book titles. Another section is an index of authors and books by each author, with a page number cross-referencing each title with its entry in the title section.
In FrameMaker, when I open the author document, I can update all the references at once by pointing to the title document.
I don't see an easy way to do this in InDesign. Is it possible to update all cross-references at once?
Furthermore, in researching the problem on the Internet, I came across multiple comments that suggested that it's not a good idea to use cross-references across multiple documents in InDesign. Is this true, or was it only a problem in previous versions of InDesign?
Thanks for the help!

I think you should head over to the scripting forum and ask over there. Dave Saunders has just finished a huge project with thousnads of cross-refs to external docs and he might have some scripting ideas that would help you.

Similar Messages

Cross-references referencing two different elements...

Is there any way a cross-reference can reference two element tags at the same time? My attributes for my xref tag calls for two reference ID tags, but when I used the Special>Cross-references menu, I am only allowed to choose one or the other... When I try and type in the UniqueID for the other one, it telle me to use the Special>cross-references menu to chose the ID... I thought that you can type the plain ID number in the attribute value to refer to...? Thanks.
Ashley

Ashley,
It seems a little unusual that you would want to do this in the first place. How can a link have two targets? You can only go one place at a time.
Russ

Display cross-references' linked documents filename in the xref panel

Our company creates technical manuals consisting of five chapters, all named the same, except with a different prefix. For example the "ABC Widget" manual has an introduction chapter named "ABC 1 - Introduction", a safety chapter named "ABC 2 - Safety", etc. Many times I re-use documents for creating subsequent manuals using the "Save As" command. So the "ABC 1 - Introduction" chapter would be saved as "EFG 1 - Introduction" for the "EFG Widget" book. For all the internal xrefs it saves a whole lot of time since all of the xrefs are preserved. But for cross-document references it creates a problem. For example, if the "ABC 1 - Introduction" chapter has a xref to "ABC 2 - Safety", when I save the Introduction chapter as "EFG 1 - Introduction" it will still retain the xref to "ABC 2 - Safety".
Right now, the only way to see if there are xrefs pointing to latent docs, is to check each one manually. If the xref panel displayed a column indicating the filename of the linked documents, I would be able to tell at a glance if that xref was pointing to the wrong document.
Thank you.
ID CS5, MAC

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross references in structured documents

Hi there,
Perhaps someone of you has a tip for me regarding cross references in structured FrameMaker.
The problem we have at the moment:
We were working with FM8 structured. But - as we worked with FM documents most of the times - very often the xml files are not on the latest version.
When we now want to update these documents with FM9 and save them as xml documents, there are lot's of errors that the attribute type is not defined for the element fm-xref.
Perhaps some of you know this error message.
At the moment we do exchange all those cross reference for new ones.
Of course, when we have a xml document which contains the latest status, this is not a problem.
You just open the xml file and save it as FM9 document. No problem with any cross reference...
But what can I do with those FM8 documents?
Would it help to use some application just for fixong the cross references in those (if possible)?
This definitly seems to be an error in FM itself.
Is there perhaps some fix for FM9 I don't know about?
And how about FM10: Will I have the same problems, if we switch to that version?
Regards,
Anna

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross-References to other documents

As Cross-refences within a document act as clickable links to their destinations when exported to PDF, can cross references to content of another Indesign documents act as clickable links to the destination after being exported. I think no, but I want to double check.

I actually tried this already, it still crashes and the error is reproducible on four different computers here: 1 Mac and 3 Windows machines. I didn't even restore my old preferences, I just did the reset and it still has the issue. Note it's not crashing when I use data merge, simply when I try to view the panel.
The only thing that differentiates this document from the other ones I've had issues with that I got my work-around to fix is that the cross-references point to other documents (where the other ones I've managed to fix have cross-references within the same document).
For the sake of my sanity I may just convert the (2) cross-references to text if they are in fact the issue.

Relinking Cross-References after Renaming Documents

I have a problem where I have created a book containing 14 chapters. Each chapter has a reference to the language of the book i.e. GB in the document title, we now want to translate the documents, so have copied the book, and chapters, renamed the document with an FR in the document titles, ready to send of to the translators.
The trouble is all the cross references are still linking to the GB book. Is there a way of re-linking all the cross references to the FR documents? Or is it a case of going to each cross-reference and re-linking to the same piece of text but in the FR book.
Can anyone help?

tRawc wrote:
I have a problem where I have created a book containing 14 chapters. Each chapter has a reference to the language of the book i.e. GB in the document title, we now want to translate the documents, so have copied the book, and chapters, renamed the document with an FR in the document titles, ready to send of to the translators.
The trouble is all the cross references are still linking to the GB book. Is there a way of re-linking all the cross references to the FR documents? Or is it a case of going to each cross-reference and re-linking to the same piece of text but in the FR book.
Can anyone help?
No help here, at least no help in providing some magic. Cross-file cross-references seem to depend on the name of the file that contains the cross-reference "destination" - the text that's captured and displayed at the "source" - the location where the cross-reference is inserted. I'm using quotation marks here because some folks think of the stuff you capture as the cross-reference source, and what's displayed at the cross-reference insertion point is the destination in their view. IOW, they're opposite uses of the term. InDesign's nomenclature is based on the hyperlink model, where you create a destination somewhere and you act on it by pointing to that destination from where you insert the link to it, AKA the source of the action. At least that's my guess.
So, changing file names loses the connection.
Internal cross-references - within a single document file - are maintained when the file's name is changed.
You can relink cross-file cross-references for files that are moved to a new folder. In the Cross-References panel, select a "missing" cross-reference that displays a question mark in a red circle, then from the panel's fly-out menu, choose Relink Cross-Reference, and browse the directory. If all the cross-file cross-references in the file whose cross-references point to files in one directory, relinking should restore all the links. If some cross-references point to files moved to other directories, you'll need to browse to each of those directories.
With a book, if all the missing cross-file cross-references for all the book's component files were all moved to the same folder, relinking one missing reference should relink all. If some missing cross-references point to files moved elsewhere, you'll need to browse for each of those directories.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

How can I get XML cross-references to translate to Structured FrameMaker?

I've been using Structured FrameMaker from the beginning, and have designed many EDDs, and about 10 years ago I did some translation of SGML into Structured FrameMaker (7.2) which worked well.
Now, (with FrameMaker 10), I've had to design an EDD to translate XML documents into Structured FrameMaker.
In my EDD I've a CrossReference element called XRef; this has an attribute of ID, which in turn has a value of IDReference and has Special AttributeConrols of ReadOnly.
My target elements in the EDD all have an ID attribute with a value of UniqueID.
My XML document's target xref element has an attribute of linkend, and in XML this works as I'd expect.
When I pass the XML file through the EDD/Template, everything works except that I get an ID = no value, which, of course, results in no display of the cross-reference data in the document.
Oddly, in structured FrameMaker, my element of link, with an attribute of linkend, works as it should, and displays the data. It may not be important, but the value for linkend is IDReference not UniqueID, and this displays correctly (I changed this attribute's value to Unique ID in my EDD and it made no difference to the XRef value in my document).
After making all these EDD changes, I've been careful to save the changes, import them to all files in my book and finally update the book.   Everything hangs together - except, of course, that the cross-reference doesn't work.
I'd sincerely appreciate any help or advice other users might have because I'm quite frankly stumped.

Russ,
Sorry about the delay in replying; got sidetracked trying to fix some FrameMaker 10 problems; on occasion, it laughs and crashes if we copy an element in a document and paste it to somewhere illegal. This doesn't happen all the time, but it might be something someone might do, so it was interesting to know.
Anyway, back to cross-references.
In our r/w rules we have:
"linkend" is fm attribute "ID";
Can we also have a similar line under the cross-reference element as:
element "xref"
     is fm cross-reference element "XRef";
     attribute "linkend" is fm property cross-reference id;
     attribute "role" is fm property cross-reference format;
At the moment the second line is:
.....attribute ID is fm property cross-reference id;
I tried adding the attribute "linkend" is fm property cross-reference id; (so that I had both linkend and ID) bit but this made no difference.
In general use cross-references work, in that it picks up data in one place in the document, e.g. WorldWideWeb, and repeats it elsewhere.   So in our xml file we have a link element with an attribute linkend which, when it's processed (ignoring the handshake code used to link the two - which could be something vague like 12345vvdog), repeats whatever is the target.
Conversely, for a cross-reference, in xml they use an xref element which also has a linkend attribute (similar mysterious secret handshake behind the scenes) which is deemed to point to a list of references.   This looks like it might be the stumbling block in that it links to an area in the xml document which is used as an internally generated list of references. Apparently this is only built when the xml book equivelent is finalised, so is not, like the link and linkend coupling described above.
I've passed this back to the xml people, and they are investigating a different way of preparing their cross-reference to a list of references (I'm now thoroughly confused with all these references - good thing the weekend's just around the corner).
I appreciate all you help and advice, I'll admit that this is a lot more difficult to understand than straight-forward EDD element creation along with their respective attributes.   Life used to be so much more simple back then!
In sum, what I thought I was doing was allowing an ID attribute with a value of IDReference in my elements, this was deemed to allow for FrameMaker cross-referencing.   In Structured FrameMaker, on its own, this works just fine; it all fell flat on its face when trying to import xml.   I tried to see whether the xref element's ID attribute could also be a UniqueID, but as just about everyone has said, this is a silly idea.   I was just trying stuff to see whether it might make a difference - you'll not be surprised to see that it didn't!
For the moment, I have attributes called ID with a value of IDReference, and I understand you're all suggesting to leave it at that.
If I understand correctly, I could eventually use an IDRef attribute if I wanted a UniqueID value to be used, though I'm not sure what a UniqueID is used or useful for, so will file that for future use.
Again, thanks for the advice and help.
Chris

Cross References in ID CC

I've seen cross reference questions, but none dealing with ID CC, which, I believe is 64-bit.
We've greatly expanded our use of cross-references with this new more power version with overall good success. However, ID still seems to insist on updating every cross-reference with every keystroke. What a pain.
I work with all book documents open to minimize this, but since it's across a network, it can still be pretty painful. In addition, some documents are used in multiple books so I use layers to control which cross-references are active any any given time.
It's getting very trying. Does anyone have experience with using 3rd party xref management software with ID CC?

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross-references in HTMLHelp

I currently have a help project which includes popup help
topics for a large number of fields in a software suite. They are
formatted as follows:
Field Name
Field Description
I also have a number of help topics that act as summaries for
sections of the software. They include field listings (using
tables) that are formatted as follows:
|
Field Name | Field Description |
|
Field Name | Field Description |
|
Field Name | Field Description |
Each field can be referenced in several different summary
pages.
Periodically, I have to update many of the field
descriptions. Is there a way for me to automatically fill in the
field descriptions in the tables, in HTML help, so that they
automatically update when I modify the descriptions in the popup
topics? The current project is in WinHelp - I am using bookmarks
and cross-references in Word to achieve this, but we're switching
over to HTML help and I haven't been able to find a way to do it
there.
Any ideas?
- Brian

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross References: CS4 to CS3

Background:
My company group uses InDesign CS3 on Windows XP for about 5% of our document needs. The small percentage is primarily due to cost and learning curve issues, but we don't push to move more documents (particularly our engineering reports) from Word to InDesign because of page numbering and cross-referencing issues. The documents are graphics heavy, so this is a shame, particularly with our 300+ page documents that end up as pdfs.
Question:
I've read that cross-referencing has been extensively beefed up in CS4. If I use CS4 to put in cross references and take my document to my CS3 what happens?

According to the Help file,
Delete cross-referencesWhen you delete a cross-reference, the source cross-reference is converted to text.1In the Cross-References section of the Hyperlinks panel, select the cross-reference or cross-references you want to delete.2Click the Delete icon, or choose Delete Hyperlink/Cross-Reference from the panel menu.3Click Yes to confirm.To completely remove a cross-reference, you can also select the cross-reference source and delete it.
"Deleting" and "completely removing" are different, and the characters composing the xref remain in the text if the xref is "deleted" ("converted to text" would be better terminology). You can select and "delete" all the xrefs in a document simultaneously, so it's a fast operation. I would then imagine that the text of the "deleted" xrefs will survive as text in ID3. You'll just have to try this last bit.
The above is no good if you have to round-trip. I think you then have to buy DTP Tools' Cross-References Pro plug-in and use it to make xrefs in ID4, ignoring ID4's built-in capacities. These xrefs should survive as xrefs in ID3 (with the same plug-in installed), tho' you might want to check with the DTP people on that to be absolutely sure. If you then go back to editing the doc in ID4, the xrefs should still be there, "live" as opposed to dead text.
Amazing that your company does tech docs in Word. Upgrading to ID4, or if you're on Windows, switching to FrameMaker, is a better way to go. There are various reports on the Web you can google that contrast Word and FM -- I bet quite a lot is applicable to Word vs ID too. You might be able to put together a persuasive budget request from them.

Scripts export information about cross references

scripts export information about cross references in the active document and saves the result to csv/txt file (es: LOIC script Links2CSV; http://www.loicaigon.com/en/solutions-en/downloads/).
I am working with a multi chapter user manual with many cross references, we need to export cross references before translating document and create it after translation in the same place.
Thanks,

Hi,
Thank you for the suggestion, but our company is world-wide and each subsidiary deals with different staff and editors (who only some use Adobe software, but all use Office). I will pass along the info though.
This would be a good Feature Request for a future release of InDesign!
Thanks again.

Cross-Reference creation

Hello to all!
I am new to this amazing world of Extendscript but I have been using Framemaker since version 5.5.
I am working on a kind of cross-reference manager and it works really nice. I can list all cross-references at book or document level, select the cross-reference to be shown in the current document and so on. I am using non-structured FM.
The problem I am facing is the creation of cross-reference itself.I know how to create a Cross-Ref Marker for the Xref, but I don´t know how to insert the Xref into the content. I tried with NewAnchoredFormattedObject function with objType, format and textLoc parameters. Also there´s the XRefSrcText property (string containg unique ID:pgf_tag:text).
The question is: Should I use the same string (the content of XRefSrcText) as text for the Cross-Ref type Marker? Or just the pgf text that contains the Cross-Ref?
I have found several examples using Framescript but I am unable to replicate the code using ES.
Thanks for reading me. I will appreciate any help on this.
Regards

Hi again Jang:
I have been trying to create the XREF following your suggestions:
First I created a XREF using the FM procedure. Then I created a code to get the info from Data Browser in the ESTK.
Then I created a XREF using my own code: FM recognizes the XREF (as you can see on the right image) but I cannot get any cross-ref on the content.
Here is the code for the Cross-ref marker target creation:
var doc = app.ActiveDoc;
var flow = doc.MainFlowInDoc;
var pgf = doc.TextSelection.beg.obj
var tLoc, marker, markerType;
tLoc = new TextLoc(pgf, 0);
marker = doc.NewAnchoredObject(Constants.FO_Marker, tLoc);
markerType = doc.GetNamedObject(Constants.FO_MarkerType, "Cross-Ref");
marker.MarkerTypeId = markerType;
marker.MarkerText = "10978: Heading1: PREAMBLE";
Here is the code I am using to create the XREF:
var doc = app.ActiveDoc;
var flow = doc.MainFlowInDoc;
var pgf = doc.TextSelection.beg.obj;
var oTLoc1=new TextLoc (pgf, 0);
var format="Page";
var newcrossref=doc.NewAnchoredFormattedXRef(format, oTLoc1);
newcrossref.XRefFmt.Name=format;
newcrossref.XRefSrcText= "10978: Heading1: PREAMBLE";
I have tried with tons of modifications but without success.
I hope you can help me!
Regards

Cross Reference Sources appearing in Story Editor view but not appearing in the Cross Ref pane

I have imported a Word document containing working cross references into an InDesign document. The vast majority of these cross references import correctly and link to their destinations within the document, however there are some that are not working. If I view the text frame in the story editor view, I can see these "broken" cross reference sources that came in from the Word doc but on selecting them I can see that there isnt a corresponding entry for it in the cross reference pane. As said, there are only a few that are behaving like this.
What could be causing these not to appear in the cross reference pane?
Obviously as they are not appearing in the list of cross references I can't update them, and also, as they are technically broken cross references, because a source exists for them but there is no corresponding entry in the pane, then on export to epub, InDesign crashes (If there is one broken cross reference in a document, export to Epub will crash indesign).
Also, to clarify, in the Word doc if I navigate to a cross reference that is failing once in InDesign, I can update it properly, and also navigate to its destination in the Word doc, so it's not as though these cross references are broken before coming into InDesign. Also I believe the destinations for these "broken" cross references are coming across properly to indesign too as I can see them in the story editor view.
Supposed Cross Reference source selected in Story Editor view on left, but no corresponding cross reference highlighted in pane on right:
Technical Details:
InDesign CS5.5 - Version 7.5.3
Microsoft Word 2010, File type .docx

I have found the possible cause of this problem!
If a table is used within the Word document somewhere between where the cross reference source is and its destination then that particular cross reference will be broken as described above in my initial post.
So the "fix" is to remove any occurances of a table in the Word document and the cross references come into InDesign perfectly. This is actually not a fix at all. I need to use tables in the Word document for layout purposes so if they break cross references if they stand between them and their destinations then I have to compromise, i.e. use tables but with no cross references in the document or vice versa.
I found a similar issue recently with index markers in Word causing a shift on the cross reference tags when bought into InDesign. The "fix" again for that was to remove all index markers from the Word document. See post about this here: http://forums.adobe.com/thread/1043981
InDesign really needs to sort out the issues with importing of Word documents with cross references in them. If I can't use index markers and tables in a Word document without breaking its cross references then they can't claim to have the ability to import a Word document while maintaining its cross references into an InDesign document. It just doesnt work as ive painstakingly proven.

Acrobat 9 Pro: Links to Word TOC and cross references are lost

I'm testing Acrobat 9 Pro and while it successfully creates a PDF from Word 2003 with bookmarks, all my TOC and internal page reference links are lost.
I have triple checked the conversion settings from the Adobe PDF menu option in Word, and the "Convert cross-references and table of contents to links" check box is definitely selected.
I used the same Word document on another machine with Acrobat 6 Pro installed - and the TOC and cross ref links were created successfully. As far as I can see the Adobe PDF settings in Word 2003 on both machines are the same - the only difference is that one uses Acrobat 6 Pro and the other uses Acrobat 9 Pro.
The only setting in 9 Pro I turned off was the 'enable accessibility tagging' one; it's also turned off in 6 Pro. The remaining settings are the default.
A clickable TOC and internal links is essential for my clients who often have 400+ page documents.
Anybody have any suggestions? Or can anybody confirm that they do/don't get the same behavior in Acrobat 9 Pro?

Thanks Abhigyan - your test PDF worked fine for me.
This is what I've done today:
1. Checked for all instances of pdfm*.dot files and removed any that were lurking in old Application Data and Microsoft Office folders.
2. Deleted all Acrobat 5 and 6 folders and subfolders still lurking in Program Files.
3. Used Add/Remove to delete Adobe Reader 8 and its updates. I figure I can always install Reader 9 if I need it as a separate app.
4. Checked that everything was gone using the Windows Installer CleanUp utility (it was).
5. Restarted my machine.
6. Turned off my anti-virus software.
7. Did a search for any pdfm*.dot files - found one only in the current Microsoft Office folder and left it there.
8. Reinstalled Acrobat 9 Professional.
9. Opened my test Word 2003 document.
10. Checked all the Acrobat conversion settings and left them as the defaults.
11. Converted the doc to PDF and checked for internal links. Yes! The TOC links worked! But my joy was short-lived as the page link didn't work...
12. Tried various other conversion settings based on some suggestions from Lance in first level Adobe Support yesterday - still no page link. And I also lost the TOC links when I cleared the Enable Accessibility check box on the Settings tab of the conversion settings.
13. Checked the Edit > Preferences > Convert To PDF settings for Word in Acrobat 9 - add bookmarks and add links are both selected (default).
14. Used Acrobat 9 to create the PDF (File > Create > From File) hoping that this might might a difference. Nope. No TOC or page links.
15. Changed conversion settings back to default via Word 2003, and created a PDF from a longer document. Again the TOC links worked, the URLs worked (they always did), the bookmarks worked (they always did too), but the none of the internal page cross-reference links worked.
So my summary is this:
* I can only create TOC links *if* Enable Accessibility is turned on, but I have always turned this off in earlier versions of Acrobat as I don't need it and it made the process of creating a PDF from a long document incredibly slow - I'm wary of using it!
* I cannot get internal page links to work at all, no matter which method I use to create the PDF (from within Word or within Acrobat), and no matter which conversion settings I select.
I really don't know what to try next. Manually creating links for what could be hundreds of cross-references in a single document is NOT an option, especially as I have many of these long documents.
Any further suggestions?

Word 2010 AAX Cross-references gone

I have 13 documents - "Word 10/AAX (all updates installed)", with many cross-references.
Links correctly translate to PDF including headings, TOC, websites, and cross-references WITHIN the same document, but cross-references between the 13 docs do not work.
The PDF shows the colour change, but there is no clickable link.
I am "Saving as PDF", have checked the PDFMaker settings, and have tried creating the PDF directly from AAX.

Hi Pranav,
Yes, this is already selected. All links are correctly created, except those which cross-reference other Word 2010 documents.
I need the PDF to maintain the cross-reference as is found in the Word Doc (which is simply a link to a specific bookmark in a separate Word Doc).
In summary: One Word Doc references a specific bookmark in a separate Word Doc - so when the PDF's are created: PDF references the specific bookmark in a separate PDF.
Any other ideas would be most appreciated. Thanks!

Cross-references in a different document

Similar Messages

Maybe you are looking for