This content has been marked as final. Show 7 replies
I'll move it back to my hard drive and just burn a CD each time I make a revision to it for back up purposes.
If your reason for having the project on the network was so you are certain it's backed up, it's fine to keep it there for that purpose. The thing you don't want to do is to open RoboHelp, open the project while it is on the network and work on it.
Most of us will keep the projects on the local C drive, work on them, then just as you would burn the CD for backup (which you may wish to do, totally up to you) we copy the updated project to the LAN so it can be included in the daily backup ritual.
The CD bit is good and I used to follow that route too. This is because it's been my experience that if you ever ask for something to be restored on the network, it doesn't happen immediately. It is much more efficient to just grab the CD and copy from there.
I completely understand what you are saying. However, we have been told we cannot have duplicate files on our hard drive and on our server. (Don't get me started on that decision!) To avoid further problems, I will just burn a CD. And as you said, if you need it quickly, it is probably better than waiting for server files to be restored.
I've now moved my project to my C: drive and am still having the same problem. This issue is further complicated because my project is in our own version control app (MKS), not RH's version control feature.
Anyone have any ideas?
Thanks for the reply and suggestion!