• Subject: Odd Printer/Print Writer question
  • From: mcrump@xxxxxxxxxxxxxx
  • Date: Thu, 25 Mar 1999 11:28:50 -0500



I have a payroll/time clock application.  We are planning on allowing employees
to inquire on their timecards and check stubs in a centralized terminal method -
I call it a kiosk.  Application security on the terminal is fairly robust with
the use of timers and badge readers.  My problem is we want to enable an
employee to print their information.

What I can't let happen is let someone print their check stub, run into some
printer problem (jam, out of paper, etc.), walk away from the kiosk, have the
problem solved, and the information prints after the employee leaves and is at
risk of being picked up by someone else.

This kind of 'process' is completely foreign to how we have operated in the
past.  I was wondering if anyone had some similar scenarios or any suggestions.
I am currently thinking of:

1.) some sort of monitor environment whereby printed information is
automatically deleted in an error situation.
2.) direct print from the application.
3.) starting and stopping the writer from within the online program with
feedback to the program on error situations.

Of course, I would like to do this with minimal or no modification to the
existing online program.....


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].