Jump to content

Mikeness

Registered Users - Approved
  • Posts

    13
  • Joined

Converted

  • FusionPro Products
    No

Mikeness's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

10

Reputation

  1. Appreciate the explanation Dan. This is massively disappointing for us, as all of our projects are always built around an Access database, and one of the main reasons why we've made the switch to FusionPro from other solutions was its ability to impose and compose in a single step. Exporting all of our queries to flat files would really bog us down as we manipulate the data in production and is therefore not a feasible solution. Having bought the software just before the Holidays, I'm not feeling too confident with the purchase... Anyways, thanks again for all you help guys. Mike
  2. Thanks so much for collecting the job. After nearly pulling all my hair out, I at least found the source of the issue, but it just creates another... When imposing an FP project where a DSN file is my data source, the imposition file creates full stacks of 100, regardless of whether or not there is enough data to fill the stack. When the FP file is linked to a CSV (simply exporting the same table that is being read in the DSN - i.e. same data), the stacking works properly... So, now that I know what's causing it, my obvious next question is why this would be a problem and if anyone knows of a workaround?
  3. I suppose I will have to. Can you please do me one last favor and post the PDF template and Imposition file? Finally, perhaps you could also take a couple of shot of your composition settings tabs? This will help me to make sure that I am absolutely not missing anything. Thanks a bunch!
  4. I'm confident this is not the case, as the file is only processing the correct number of records. Also, no blanks are created when we Compose without using imposition. Perhaps the problem is not in the imposition file, but it's not caused by blank records (all data is actually exported from Access where blanks are easily seen). I've created a template PDF for illustration purposes and attached it so you may see the output. We're running FP 9.3.9 on Windows XP. Really want to get to the bottom of this as it is really prohibiting us from implementing FP in our production process. ImposeTest-Output2.pdf
  5. I'll create something that I can post, but that seems to be the case. The file comes out printed 2-up for the first few sheets and then reverts to 1-up for the balance as there are not enough records to fill 2-up over the full stack.
  6. No I do not have any chunking rules setup. We we're simply applying the "Record per file" option in composition. I had a look at your imposition file and I can't seem to find a difference between your file and mine other than the infinite stack option. When I remove the Infinite stack, the imposed final file, which contains 166 records, continues to output 100 sheets (or 200 pages duplex) rather than the 86 I need. 200 records is the max file output we've assigned. When I check the Infinite Stack option, I get an error when composing.
  7. Hmmm... something strange going on here. Can you post that imposition file? And perhaps a quick shot of your Composition setting too? Big thanks.
  8. If I uncheck the Infinite stack option, my last batch file will contain 100 sheets even though it only though I would only require 86 (batch size is 200, 200, 166 records per batch respectively @ 2-up duplex). We basically need the software to adjust the last batch (each batch in a separate PDF file) to not waste any sheets.
  9. We're stacking 1-100 then 101-200. I've posted our imposition file and a screenshot of our Output setting in Composition Settings. Perhaps I'm making a blatant error somewhere? Appreciate the help! TestImpose.fpi
  10. Hi all, We would like to begin imposing using FusionPro to simplify production but have run into an issue regarding stack size on the final batch. The document is to be printed 2-up, duplex, and we have a total of 566 records. The shop has asked for stacks of 100 sheets per batch. We therefore would output 3 pdf files of 200, 200 and 166 records respectively. This works fine up until the last batch where the imposer continues to create a PDF of 100 sheets when only 83 are required. I've tried activating the InfiniteStack option combined with "Output to multiple files" in the composition settings and constantly hit a wall due to chunk size. What is the recommended way to go about setting this up? I would ideally like to avoid writing any script to do this, as it can make it difficult to pass onto production staff to manage. Thanks!
  11. I've read through all the available posts but just can't seem to get this functionality to work. I have a two page PDF template, loaded with 7 PDF resources, 2 of which are two-page documents while the balance are 1 page. I've setup a variable graphic frame on both pages and assigned a switch rule based on the "Version" field in our .mdb file. The following rule works fine to call the first page of the PDF, however I can't seem to apply the pagenumber function to this structure. I've highlighted the two 2-page resources with red text. What is the most straightforward method to be able to call on the second page of the resource in the second variable graphic frame? Rule for page 1 that works well: switch (Field("Version").toLowerCase()) { case "NA".toLowerCase(): return Resource("NA"); case "NB".toLowerCase(): return Resource("NB"); case "TEB".toLowerCase(): return Resource("TEB"); case "TEC".toLowerCase(): return Resource("TEC"); case "TFA".toLowerCase(): return Resource("TFA"); case "TFB".toLowerCase(): return Resource("TFB"); case "TFC".toLowerCase(): return Resource("TFC"); default: return ""; }
×
×
  • Create New...