This content has been marked as final. Show 4 replies
I'm not sure how you'll accomplish this, but you must again attempt to convince your Manager that if you continue to work against recommended best practice, you will continue to experience problems. In addition, successive RH sessions can produce entirely different problems from previous sessions. And quite honestly, I doubt that different Access versions will have any effect on this perennial bugaboo.
It is an Access 97 database but Leon is right. If you ignore the recommendations, it's going to break. Do you keep banging your head against a wall or do you eventually figure it hurts? :-)
K, I'm going to play "dumb" here. Since I'm new to RoboHelp what are the best practices?
Thanks Leon and Peter. This has been very helpful. You guys are great.
"We are running our application and project from a VM . . ."
If you are referring to the RH application, that's not good. But if you're referring to the application for which you are writing help files, you can run that application anywhere you want, because RH is totally unconnected with it.
Once you generate the help output files, those are the ones that should be on the same server, if your manager wants it that way.
The "best practices" are those you have already read, recommending that RH and its source projects be kept on a local hard drive, and not shared across a network.
As an exception, also covered on Peter's site, you can keep the project files in a version management system on a network drive, but you must check everything out to the local drive for editing, and check them back in for version control.