Personally, in a situation like this I would be inclined to somehow engineer out the pdfs altogether maybe converting them to RH topics and generally try and achieve as clean a starting point as possible.
Thanks for the suggestion, I wish I could say that was an option but I am talking about over 3,000 .pdf files. Honestly, I dont believe it to be the actual PDF files themselves, maybe just the name and/or characters that make up the name of them. The PDF's are product labels, so its not really a structured PDF document. I need them as baggage because the users must search information within them such as UPC number and so forth.
Welcome to our community, Nathan.
I could easily see odd characters in the file names causing an issue. With RoboHelp HTML, any odd characters in any file name can be suspect.
For what it's worth, I consider any character other than A-Z, a-z or 0-9 to be considered an odd character. Except for the underscore. The underscore is often used in substitution of a space.
Helpful and Handy Links
Thanks for the welcome . I noticed a lot of the document names with (& , - _, .), I know for sure it doesnt like % and &. I guess Im going to have to go slow and just rename all these documents, do a section, compile/backup and keep doing that.
Here is an example of one of the names of the PDF's:
I realise you are using RoboHelp 8 but this thread may interest you. http://forums.adobe.com/message/3413332#3413332
Flaven had a problem upgrading to RoboHelp 9 that caused it to crash. The project was looked at by Adobe who identified the cause was PDF files.
Their troubleshooting was the good old method of copying the project and trashing half of it. If it then worked, the problem was in the half deleted so you repeat the process with that half.
I know with the number of PDFs you have, that is not what you want to hear but it may be what you need to do.
See www.grainge.org for RoboHelp and Authoring tips
64 characters, including the extension? Yikes! And I'll bet that the directory path to that file must be at least as long!
Do yourself a favor, and try reducing these paths as much as possible (and don't use ampersands, spaces, etc.).