Whilst RoboWizard's understanding of the TOC issue may have
been better but looks like one of my thoughts was spot on! RoboHelp
projects must NOT be worked on when on a network drive. The project
must be local. Also you should generate the outputs locally and not
to a network drive.
To get your help onto the server, you then either publish
from RoboHelp, the last page of the wizard, or you copy the files
by whatever means suits you to the server. Do not generate to a
server.
Almost certainly this is the cause of all the problems.
RoboHelp is underpinned by an Access database and they do not work
well across networks.
Problem now is that moving it locally will likely not correct
the mess that has occurred. See the last paragraph of my first
response.
1] Download and install the update RoboWizard refers to.
2] Move the project locally and create another copy of it.
You may need to use that if the next steps don't go well.
3] Try my suggestions for correcting things. I am assuming
too many changes have been made since the project was last backed
up and good.
If you hit further problems, post back and we'll try to point
you in the right direction.
RoboWizard: How filthy rich are we now with £1 / $2 for
every network based problem? I'll look for your reply when I get
back from the Merc dealer.
Sorry to tease James. As a new user you were not to know but
I make the point this way so that you and anyone else seeing this
thread knows we are not kidding on this one. Networks are a no no
unless used with source control.
Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.