Re: Margins are way off, can not be changed in Access 2003

Sounds like the printers margin. Some printers can't print as close to the
edge as other printers, you might want to check the printer manuall.


"JBall" <JBall@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CC323A9F-090A-4965-B1E6-0E585BEAAF65@xxxxxxxxxxxxxxxx
> My default printer is a HP laser, reports work okay on it. When I specify
> another printer for a report, the margins change to 5.095 bottom and 4.096
> right. The margins for top and left are okay. When I change the bottom or
> right, the margin changes back to above.


.

Relevant Pages

  • Re: VB Printer Dialog Problem (VB6)
    ... margin", which on many printers is itself a little to the right of the left ... value of 12, Call SetMargin. ... the very bottom most position you can ...
    (comp.lang.basic.visual.misc)
  • Re: Word setting huge bottom margin
    ... This problem is in the Preferences, and an Archive/Install keeps the ... I have 5 identical Intel minis printing to a couple of HP printers (P2015, ... and if you then do Fix, it changes the bottom margin to 18.37". ...
    (microsoft.public.mac.office.word)
  • Need suggestions for a printer.
    ... After checking out several printers and flipping through various ... The fact that the bottom margin is ... Takes pigment black ink. ... If it doesn't take giant cartridges, ...
    (comp.periphs.printers)
  • Re: Printer paper margin problem
    ... Chris Evans wrote: ... When I do a printout from TechWriter/EasyWriter the margin on ... The top margin is correct. ... I've tried editing paper margins for various printers over the last few ...
    (comp.sys.acorn.hardware)
  • Re: VB Printer Dialog Problem (VB6)
    ... And the right margin as well. ... I tested KillDoc here just on a very simple print job and it worked fine, but I had visions of it causing problems with more complex print jobs and possibly on certain specific printers. ... But my suggested method of altering the CurrentX and CurrentY positions instead of actually printing the stuff and then setting them to zero instead of doing a NewPage works fine and is reliable: ...
    (comp.lang.basic.visual.misc)