>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.

Right. Last few times I had to do it that way (back in... early nineties probably, and that was FPD then) it was both a huge PITA to do, and also printer-specific, so what worked in one setup wouldn't work in another.

Even if you get a few sets of control sequences, _PDSetup style, that's still one set per printer type, and it could just blow on the next Windows printer, where the whole rendering is done by Windows, not by printer.