By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,657 Members | 1,029 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,657 IT Pros & Developers. It's quick & easy.

A seasoned report I've used for 1.5 years has started misprinting

P: n/a
MLH
I have a report that prints onto Avery labels (3-across
by 10-down) on a standard 8.5x11 sheet of labels. I've
used it for nearly 2-years. Recently, I made some changes
to the A97 database. I don't think any of them were to
the report or to the table that feeds it. But hey - who knows?
Until now, there have been no problems like this one.

Here's what's happened - The first line in the 8th label starts
about 2-inches to the left of where it should. If you count the
labels left-to-right beginning in the top row on the sheet, it is
the 2nd label in the 3rd row. Instead of printing on the middle
label, its over to the left about 2-inches. It and the 9th label
are similarly misaligned.

Each label has 4-lines. There are 4-fields in the source table
(tblCertMailLabels). Nothing is goofy elsewhere. All other lines
on all other labels are fine. If I print preview the labels - they
are perfect. If I print to a PDF virtual printer, they print fine. To
me, that suggests printer problem. But I can't be sure. Hoping
for some feedback here.
Apr 10 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
MLH
I have narrowed down this unusual problem. You're
gonna get a kick out-a-this.

The 3rd line of my label is a concatenation of City
State Zip. More exactly, it was a concat like this:

[MailCity] & ", " & [MailState] & " " & [MailZip]

Now, believe it or not, the dbl-space between state
and zip was the root of all evil. I could have MUCH
longer strings in that control and produce reports w/o
any problem as described in O.P. But MUCH shorter
strings with DBL-SPACE present led to justification
problems in the NEXT label in line to be printed.

WOW. I couldn't beleve my eyes. Manually typing
strings into my source table confirmed and proved
beyond a shadow of a doubt that misprinted labels
occurred when I put dbl-spaces in immediately
preceeding label field(s).

Problem solved. Issue still stands. Am using HP
LaserJet 4200. Maybe this is driver-specific. I did
creae a perfect printout using a PDF printer driver
- even with the dbl-spaces.
Apr 10 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.