I was wondering if anyone can provide a list of reasons why a robohelp project should not be worked on while saved to a network drive. I can't seem to find anything in the robohelp documentation that states why this shouldn't be done.
Who said it cannot be worked on while saved to a network drive? That was the case many years ago but that changed several versions back. The only limitation that Adobe cautioned about was the speed of the network and that is outside their control.
You haven't said what version you are using but unless you are using a very old version, you need to try it. Until you are satisfied your network is OK, then keep regular backups.
Hello Peter, Thank you for your quick response. I am using Robohelp 2017. The biggest problem we tend to have is latency (which is really, really slow). I guess some of the posts I have read were probably outdated. One other issue that I have come across which I discussed in this post, is that if I import an image into robohelp, it will place the image into the top-level project folder instead of the folder of the topic I insert the image into. I was wondering if there might be any other odd behavior I should be aware of while working on a project in a shared network drive?
Thank you. I appreciate your help.
The location of the project typically has nothing whatsoever to do with where images are stored when you add them. They have always been added at the root level of the project.
However, I think this may have changed in the all new 2019 release. I believe in that release images are now in a special folder named assets.
You'd have to work with your network engineers for any latency issues. It's not something Robohelp can affect, and I don't think any of us are network engineers. 🙂