Is there a "miscellaneous project links" file?

[kevinmcl]

Our source is the source (both Content and Project files) for two or three versions of a given product's docs.
In the Projects, they are separated by named folders for each version.

As I'm checking a batch target (.flbat) I see that it has entries (checked or not checked, for "Build" or "Publish") for all the HTML5 and PDF targets for both the current and earlier docsets. That's expected. They are all in that same overall folder, and Flare obligingly finds them and offers them as selectable (check box) options to be published by the batch target.

What is not expected, if I look at "View Links" for a given batch target is that it has Linked From incoming links from the earlier version of itself.

If I fire up my trusty Notepad++ and search the earlier batch target file, it has NO MENTION of the newer version of itself. So, where is flare seeing this incoming link from the older batch target to the new/current batch target (flbat) file?

Is there a special Project file somewhere that holds a "repository of obscure links"?

This is not causing any obvious problems, just now, but ignoring mysteries tends to bring them back later (always at deadline time) to bite my butt. So... where would such a link (found by View Links) be kept? Why? How would it even get made?

[NorthEast]

Flare stores this in a database in the Analyzer folder.

If you think what's displayed is incorrect, then close Flare and delete the project's Analyzer folder.
Flare will rebuild the database when you open the project, which takes a minute or two.