Steven

all messages by user

4/18/2011
Topic:
Duplexing

Steven
Hi,

When printing from our HAS to the PrintBoss 50 print device and there are enough line items in the voucher area to wrap to multiple pages, how can I get the form file to place every "even" page number on the "back" section of the page? Currently the second page is treated as a brand new document rather than being placed on the backside of the page. It seems to do this properly when fed data from a text file capture spec, but not when printing from the HAS. Any help is greatly appreciated.

Thanks
edited by steven on 4/18/2011
<em>edited by steven on 4/18/2011</em>
4/25/2011
Topic:
Duplexing

Steven
Hi Paula,

Thanks for the reply. This solution however doesn't seem to accomplish what I am trying to do. What I'd like is for each even page to be placed on the back side of the document, so that when I view the document under "Open Document Work Files", I can click the "Back" button and view the contents of the second page. I'm not concerned with printing to a physical printer just yet, as I'd like to first get this step working properly. As mentioned, there was no special configuration needed when we were using the "Text File Capture Spec". The form file would place items on the back side of the page as needed. I would like to accomplish the same thing with the PrintBoss 50 print device. If I send a print job that is 3 pages, for example, with the PB#INFO tag just on the first page, I'd like only two PrintBoss documents (under Document Work Files) to be created. I'd like the contents of the second page placed on the "Back" portion of the first document and the contents of the third page to be on the front portion of the second document. Currently when printing multiple pages to the PrintBoss 50 device it treats each page of the print job as a brand new document and is not utilizing the Back portion of the document, despite having the "Enable Printing on Back of page (Requires Duplexing Printer)" option checked on the "Special Controls" tab of the form file.

As far as printing to physical printers, the duplexing works just fine with our current settings. That is, however, using the text file capture spec to bring data into PrintBoss.

I hope this better explains the issue I am having. If you need any clarification please let me know.

Thank you
6/27/2011
Topic:
Margins

Steven
Hi,

I'm currently working on capturing content from a pre-formatted report generated by our HAS and using it for the voucher section of a cheque. The report has .2 inch margins in the top, left and right sides. When PrintBoss does the capture, it also applies a .2 inch margin to the document, causing some content to be "chopped" off of the right side of the document. I realize there is an option to change the captured text treatment in the Form File settings, but this has not been able to solve the issue. Adjusting the X offset of the captured text seems to be applied "post-capture", so the text has already been chopped by the time the offset is applied. What I'm wondering is if there is some place in the form file settings to manually adjust the margins on the page? I'd like to avoid needing to removing the margins on the report from the HAS.

Thanks in advance for any assistance.

-Steve
7/6/2011
Topic:
Margins

Steven
Hi Paula,

thanks for the info. I'll post back if I need any more assistance.

-Steve
3/20/2013
Topic:
Managing Archive Files

Steven
Hi there,

My company is looking for a way to split and merge the archive files. Here are our scenarios:

We have work files that were archived into the "wrong" database, so there are multiple archives that need to be merged into one.

We have nearly a decade of history in several of our archive files, so whenever we need to find one item for audit purposes it can be quite a daunting task to find it. We would like to split the archive into several smaller archives by year.

From what I can tell, there is no native functionality built into PrintBoss to accomplish this. I'm looking for advice or suggestions on any 3rd party tools that can do these types of DBF managing while maintaining their compatibility with PrintBoss.

Thanks in advance for any help!

-Steven
3/22/2013
Topic:
Managing Archive Files

Steven
Nancy,

Thanks for the reply. I wasn't aware of this option, and it may be useful going forward.

What we've discovered as a solution for cleaning up our historical data is making copies of our archive files, moving them back into the Work folder, and then re-archiving them into the correct archive. This seems to serve well as a means of managing our archive files, giving us the ability to split/merge.

-Steven
12/10/2013
Topic:
Duplexing

Steven
Hello,
After more than two years, the project we're revisiting the issue that prompted me to start this thread about duplexing.
First, I'll give an update. I tried the suggestion of disabling the "Enable printing on back of page" for the form file being used. I then added the #[=e, {DocNo}, {Next.DocNo}]ForceWinPrintJob line to the beginning of the Runtime Objects tab as was suggested. I was successful in getting the print job to duplex. The problem is that if a document (i.e. document 1) has an un-even number of pages, document 2 will begin printing on the back of the last page of document 1. I can solve this by inserting a blank page between documents that get sent to PrintBoss via the PrintBoss 50 driver, however I would prefer that this be handled by PrintBoss's printing process. Is this not what the condition is for that gets evaluated before calling ForceWinPrintJob above?

Any advice on this is appreciated.

Thanks Again
12/10/2013
Topic:
Margins

Steven
Hello,

I noticed that there seems to be a quarter-inch margin that is applied to all documents received by PrintBoss. What we're doing is sending a pre-formatted document to PrintBoss using the PrintBoss 50 print driver and relying on PrintBoss for adding some of the cheque details and MICR. Ideally we would like the margins to be defined by the report and have PrintBoss not apply any margins.

Can someone let me know if this is possible?

Thanks
12/12/2013
Topic:
Margins

Steven
Thanks for clarifying.
12/12/2013
Topic:
Duplexing

Steven
Hi Nancy,
I am still having the same result using the modified logic.
It was mentioned that the DocNo needs to be captured. I send a PB#INFO trigger line on the first page of each document which contains the DocNo. Is this sufficient or do I need to specifically assign a DocNo for each page of a multi-paged document? When viewing the list of documents in the work file, the DocNo is indeed assigned correctly to each page in the document, so it looks correct to me.
3/18/2016
Topic:
Text Input File Specs

Steven
We just upgraded from version 5.73.2 to version 6.01.2 and we're experiencing a change in the way our Text Input Files are processed. Specifically, the {TextCaptDocPageNo} variable is not getting reset to 1 for each new document in the batch, so only the first document is getting a check printed for it, while the remainder of the documents are not. Any idea what could have changed in the software to cause this behavior? I understand there may not be enough information in my post to investigate the issue, so let me know what additional info may be required. We've been using the same Text Input File Specs for 10+ years without issue so it looks as though a change in the software has caused this issue.

Thanks in advance for any assistance.
7/6/2017
Topic:
Text Input File Specs

Steven
Update on this issue: We've finally upgraded to the latest version (6.02.1 currently) and are still experiencing issues with cheques produced from text input files. The original bug reported has been corrected, but there is a new bug present which is affecting the {LastPageDocNo} variable. Specifically, it is always getting assigned the same value as {DocNo}, so our "New-Page Macro" is not being evaluated correctly. This is resulting in multi-page cheque vouchers printing incorrectly. Please investigate and let me know what additional information you require.
Thanks
7/11/2017
Topic:
Text Input File Specs

Steven
Company name is Group Medical Services. Here is the New-Page Macro that previously worked and now does not:

(At("~", "{LineVal}")>0) .or. ( "{DocNo}."<>"{LastPageDocNo}." .and. {LineCount}= Iif(.t.,52,32) )

The "{DocNo}" <> "{LastPageDocNo}" condition is now always being evaluated as true because the {LastPageDocNo} variable is always taking on the same value as {DocNo}. I even added both of these variables to the form file as text in order to actually see what was happening. Before we upgraded, {LastPageDocNo} would behave as expected. Let me know if you need me to provide any additional details or files.
1




Powered by Jitbit Forum 8.3.8.0 © 2006-2013 Jitbit Software