nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Check alignment wrong for 2nd, 3rd checks

jg70124

Recently moved Quicken to a new computer. Same printer driver, same Windows version, same Quicken version, same Quicken file. I use 3 to a page wallet checks. On the old computer, I could find an alignment that would print all 3 checks correctly. On the new computer, if I align the top check correctly, the bottom 2 are incorrect - both print too high. And it's cumulative - the middle check is a little too high, the bottom check is much too high.

Is there any way to put in different alignment values for each check on the page?

Any other ideas?

Find more posts tagged with

Accepted answers

jg70124

The setups appeared to be the same... but upon further inspection, it turns out that Windows on the new PC had switched the port for the network-attached printer from TCP/IP to WSD. Once I switched it back, the checks printed exactly the same.

(A few threads around the Internet about Windows unexpectedly manhandling printer ports this way...)

All comments

NotACPA

On the new computer, what are you using at the "Check Setup"? FILE, Printer Setup, For printing checks.

Make sure that such agrees with what's on your old computer.

jg70124

NotACPA

@jg70124 Thanks for the add'l info re: WSD

Berklee

@jg70124 I have experienced identical problem as you on my Brother HL-L6200DW printer. Initially it was working but after driver update, I started seeing shifting alignment.
My post... https://community.quicken.com/discussion/7895133/progressive-loss-of-printer-alignment-across-2nd-and-3rd-check

My printer has the WSD port assigned to the driver. I tried to switch to TCP-IP port, and established connection with the printer but when I attempt to print a test page, the printer just keeps feeding pages and has to be reset. So I cannot switch to TCP-IP.

I put in a ticket with Quicken, as I expect this problem will be more common and the workaround did not solve my problem.