It sounds like you want to revert to the previous version of the document (a
good argument for a revision control system). 



Fred's second suggestion of moving the cross reference marker is a good one,
but you'd better make sure that not cross refs exist that are supposed to go
to the location that you are moving the marker from. Otherwise, you'd be
creating new "bad" xrefs.

Craig

From: [email protected]
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Fred Ridder
Sent: Thursday, June 21, 2012 10:14 AM
To: amakeler at gmail.com; framers at lists.frameusers.com
Subject: RE: FM 7.2: Is there a way to Find a cross-ref and Replace it with
another cross-ref?



If you create one instance of the correct cross-reference, you can copy that
to the clipboard, and then do a Find/Change that uses the "By Pasting"
option in the Change box. You'll still have to look at each cross-reference
you find to see if it is one you need to change, but at least you can paste
in the correct x-ref rather than having to reconstruct it manually.

Or if all the cross-references that point to the "different" target are
incorrect, you can select and cut the cross-reference marker at that
incorrect location and then paste it into the correct location. (Cutting and
pasting the cross-reference marker into a different location is the most
likely cause of the kind of problem you describe, and this is the direct way
of undoing that kind of issue.)

-Fred Ridder


  _____  

Date: Thu, 21 Jun 2012 18:01:22 +0300
Subject: FM 7.2: Is there a way to Find a cross-ref and Replace it with
another cross-ref?
From: [email protected]
To: framers at lists.frameusers.com

Hi all,



FM 7.2: Is there a way to Find a cross-ref and Replace it with another
cross-ref?



A blooper occurred in an FM doc, wherein a whole lot of cross-refs (all
pointing to the same target) got replaced by a different cross-ref. 



TIA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20120621/f855d978/attachment.html>

Reply via email to