Thanks a lot for the encourangement to bite the bullet, Dan and Dragan.

As I said before, my customers often print checks in dot matrix printers and I want that printing to be done in character mode and not graphic mode, if that is what they are called. In the past I've accomplished that by saving report to disk ASCII and then printing the file, which would bring me right back to the beginning problem of control characters.

We could have different frx's for dot matrix and laser, but I'd prefer not to do that.

Any suggestions? Thanks.

Alex


Alex

>To be honest, you should bite the bullet and convert your check printing routines to an FRX. Let the Windows print system handle what it's good at handling.
>
>Our vertical market app probably prints a million checks (with quite detailed stubs) every week at customer sites all over the US. We NEVER have a problem with printer incompatibility (except when the printer driver blows up, but that's a setup issue and it's not our issue).
>
>Let Windows do one of the few things it is good at doing.
>
>Dan
>
>
>
>>Hello,
>>
>>We have some older code to print checks and stubs in @SAY style. It is convenient to keep it that way because it makes it easy to customize position of name, amount, date etc, as well as check and stub sizes, use custom stub content, and print to dot matrix printers which our customers often use for checks.
>>
>>I found out the necessary PCL printer control sequences for normal/condensed text, set page size etc, but new types of laser and bubble jet printers are appearing that don't respond to either the old (DOS?) or the PCL control character sequences.
>>
>>Does anyone know what other "standard" or common control character sequences exist?
>>
>>Thank you.
>>
>>Alex