This content has been marked as final. Show 4 replies
The only management requirement is that some of the topics in the project are not required in the new project? If so why not just exclude them those topics using build tags?
Can you establish whether these projects will always be loaded into the same directory structure? If you can, you could make the link(s) relative, not absolute, just as you would when linking between folders in a single project, or linking between projects in a merged project.
A link from: C:\my_project\folder_name\Department_Manual.htm
would be: href="../otherfoldername/Company_Manual.htm"
I'll try your idea too. I'm currently working on a copy of the current file to try these ideas- currently I'm using Peter's, but I now can see where I was going wrong with my linking syntax!
This is odd -
I've created a conditional build-tag called FINANCE, and one called EVERYTHING ELSE. So I've assigned FINANCE to just that Dept, and all others get the EVERYTHING ELSE tag.
No when I compile it using the criteria, it does work perfectly - with one exception. The resulting build gives me the Finance Dept, but also one of the other depts - it's always the same one....'Food and Beverage' which of course falls under the 'EVERYTHING ELSE' tag.
I cleared all the Conditional Build tags before doing the above, and saved the project before going any further.
This only happens for the web based version, generating *.DOC, *.PDF using the same tags does not exhibit this problem...
Now I'm confused......
Any ideas folks??