Absolutely "separate folders for each product and each guide." Create a new layout for each deliverable, with its own destination path. Once you've done that, you can generate multiple layouts in batch mode, if you like.
Are you outputting these two guides to the same folder AND file name - perhaps using different build tags? If so that is the reason. You'll have to either specify a different folder or file name. You may be interested to know that you can duplicate the relevant single source layout and just change the output file location (and build tags) as required. Click here to see how.
Read the RoboColum(n).
Thank you for your replies. I have 7 RH projects. I have 2-4 printed layouts for each project (a user guide and reference guide for my company and a user guide and reference guide for our partner company with an output structure like so:
So as you can see, the .docs are named differently but are going to the same adminguide or userguide folder. The result is RH only allows one .doc file in the userguide or adminguide folder at a time. RH is overriding whatever is in the folder, regardless of the file name. I'm trying to avoid the following structure:
Oh, yes, I remember this one. It used to make me nuts - I could swear I had different .doc names specified in the output path, but I'd get a cleared folder anyway. I feel your pain.
I recommend making the individual folder structure. Figuring out how to get RH to stop doing this would be a triumph, yes, but think of the stress you will save yourself if you go for the safer (albeit untidier) option.