I have a page layout that has a front page and a normal page. The front page has a graphic embedded into it at the top. My project is on the network, and the image is in the project's Contents|Resources|Images folder.
When I build my PDF output from Flare, the image will only show up if the Output folder is on my local computer's C drive. If I build the output on a network drive, even in the Output folder within the project structure, the PDF doesn't display the image at the top.
What in the world am I doing wrong? Does anyone know why an image would appear when built to a local target (C drive) but not when built to a network target?
Header Image showing in PDF locally but not over network
Header Image showing in PDF locally but not over network
Victoria Clarke
-
garyjgeoaccess
- Sr. Propeller Head
- Posts: 148
- Joined: Mon Feb 16, 2009 3:23 pm
Re: Header Image showing in PDF locally but not over network
I ran into a situation in which the page layout images would disappear if I used any output path other than the default. This might be the same problem that you're having. I said heck with naming the output folder and started always using the default. Since then, I've had no problems getting the page layout images to appear in PDFs. Of course, that means I haven't really confronted the problem yet and figured out what's causing it.
I need to do some more testing. It could be a Flare bug.
I need to do some more testing. It could be a Flare bug.
Re: Header Image showing in PDF locally but not over network
Thanks - believe it or not, that's the answer I got from Flare support a few hours ago. Don't name the output path. Just use the default. It fixed the problem. I'm going to say that this is definitely a bug. Time to log I guess
Thanks for your response!
Victoria Clarke
-
garyjgeoaccess
- Sr. Propeller Head
- Posts: 148
- Joined: Mon Feb 16, 2009 3:23 pm
Re: Header Image showing in PDF locally but not over network
Thanks for letting me know. That'll same me from further testing (which could have taken a couple hours). Yes, it's time to report this as a bug--although it sounds like Flare support already knows about it. Thanks.