Skip to main content
Mark Southee
Inspiring
March 11, 2013
Answered

RoboHelp 10 Crashes consistently when trying to delete linked FM11 book

  • March 11, 2013
  • 1 reply
  • 7044 views

I have a linked project where RoboHelp absolutely refuses to display part of a topic and some of the images. So I decided to delete the linked FM book file and start again from scratch (this was a FM10/RH9 project originally). This causes RH to crash consistently. Any ideas?

This topic has been closed for replies.
Correct answer Jeff_Coatsworth

Sorry to add to the list of problems, but how come a Cross-Reference conversion setting works properly in some places, but not in others (for the exact same cross reference style - Heading & Page). This is happening on the same page.

The second example is exactly the same cross reference setting in FM as the first, but this is not getting converted at all (no hyperlink inserted!)


@Mark - this is probably the result of the "secret" limit on path and file links that I've run into before - move your source FM content into a shorter path and the xrefs will work again.

1 reply

Jeff_Coatsworth
Community Expert
Community Expert
March 11, 2013

Try importing as an experiment to see if RH will accept the FM content that way.

Mark Southee
Inspiring
March 11, 2013

Hi Jeff,

Yes, importing the FM book into a new project has worked. But is there a way of 'fixing' my current linked project?

Jeff_Coatsworth
Community Expert
Community Expert
March 12, 2013

@Mark

Can you please confirm that I am following correctly.

  • The same link worked with Rh9/Fm10
  • The same link works in a new Rh project
  • It only fails in your existing project.
  • You have tried generating to a new folder.

@Jeff

Is it possible that Mark's Project Settings for Linking did not get upgraded and something needs checking there? A wild guess on my part.


See www.grainge.org for RoboHelp and Authoring tips

@petergrainge


@Peter - possibly, but I've never heard of it happening before; looking at Mark's post on the xrefs, I'm suspecting the same "length" bug may be at play. If your source FM content is on a path that is too long (just exactly what is too long seems to be a secret on Adobe's part, but way less than 255 characters; somewhere around 30-35 seems to make it go tilt) all sorts of things seem to fall off the radar when brought into RH.