Building PDF target still thinks previous PDF is open

[rjhoughton]

In Flare 6, with Adobe Acrobat Professional 7, I get the following message when generating a PDF target:

Internal Error: The process cannot access the file ."xxxxxx" because it is being used by another process.

Things to know:

- The file it is referring to IS NOT OPEN.
- The only way to get rid of this error (it will keep generating this error endlessly) is to close out Adobe Acrobat Professional.
- This did NOT happen in Flare 5.

I'm also using Windows 7 (as I was when using Flare 5).

Thoughts?

Rachel

[LTinker68]

Flare doesn't need Acrobat on your system in order to generate the PDF. However, if you have Acrobat open, it might be causing a conflict because they might both use the backend process that's used to generate the PDF.

[rjhoughton]

But why is it doing it now, when it didn't before in Flare 5?

To me, it's unrealistic to think that I have to close out Acrobat every time I want to generate a new PDF, just because Flare isn't sensing that the file has been closed. Especially when I didn't have to in the last release.

Guess that's my workaround for now, but it's irritating.

Rachel

[LTinker68]

If that solution works, then the most obvious explanation is that they changed the backend process in v6. Maybe to fix bugs or streamline the process. I think the file sizes are supposed to be smaller. If there were other improvements, then they may have required changes to the code that require Acrobat to not be running anymore.

Of course, checking that Acrobat is running and giving you a nice message saying that Acrobat needs to be shut down before it tries to build would be nice. Make sure you submit a bug report at http://www.madcapsoftware.com/bugs/submit.aspx.

[rjhoughton]

I submitted a bug report.

Thanks for the link!

Rachel