Practical problem
We have developed our application for car park management using report
builder to print out serialised tickets. The problem we have is the tickets
are enclosed in a type of seal plastic envelope and are very thick. We are
using an Epson FX-890 with a 250 sheet feeder. The feed only takes 35
tickets.
The first question is do any of you guy know of a dot matrix that will take
maybe 100 of our tickets via a feeder?.
The other problem we have is if the feeder sends 2 tickets through the
thickness of the two tickets jams the print head. When the paper path is
cleared the print head has been 'moved' to the left and the printing is off
centre.
To cure the problem we have to switch the printer on and off. This screws
the print queue. We either get garbage out or the increment of the tickets
go astray.
Is there a way to hole the print queue until a ticket has been printed. When
I watch the print manager the number printer is always ahead of what has
printed.(presumably jobs sent to the printer buffer).
Any help appreciated.
builder to print out serialised tickets. The problem we have is the tickets
are enclosed in a type of seal plastic envelope and are very thick. We are
using an Epson FX-890 with a 250 sheet feeder. The feed only takes 35
tickets.
The first question is do any of you guy know of a dot matrix that will take
maybe 100 of our tickets via a feeder?.
The other problem we have is if the feeder sends 2 tickets through the
thickness of the two tickets jams the print head. When the paper path is
cleared the print head has been 'moved' to the left and the printing is off
centre.
To cure the problem we have to switch the printer on and off. This screws
the print queue. We either get garbage out or the increment of the tickets
go astray.
Is there a way to hole the print queue until a ticket has been printed. When
I watch the print manager the number printer is always ahead of what has
printed.(presumably jobs sent to the printer buffer).
Any help appreciated.
This discussion has been closed.
Comments
ReportBuilder uses the Windows API to communicate with your printer, it does
not have direct control over the print queue. You could possibly try
setting up different print jobs for each ticket. If you change your
datasource to only return a single ticket per report, you could loop
through, run and print each report individually, essentially separating the
print jobs.
Other than that, you may try looking at the driver options of this specific
printer. It sounds like there may be a setting that is causing this
behavior.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com