Problem when setting Zoom to False

[mcomp72]

I have a sub that prepares a sheet to be printed. Several sheets share this sub, as they all need to have the same Print Area, etc. This sub gets called each time one of the sheets needs to be printed. I've run across a problem that only happens when I'm stepping through my code.

Here's the chunk of code in question.

PrintAreaRange = "C4:" & LastColumnLetter & "213"

With ThisWorkbook.Sheets(SheetName).PageSetup

    .PrintArea = Range(PrintAreaRange).Address
    .Orientation = xlLandscape
    .Zoom = False
    .FitToPagesWide = 1
    .FitToPagesTall = False
    .PrintTitleRows = "$4:$9"

End With

If I run the code normally, it works fine. However, if I'm stepping through the code, after the .Zoom = False line, I get the following message on Excel:

The number must be between 10 and 400. Try again by entering a number in this range.

(I believe I found this code on this forum somewhere a few months back and adjusted it to fit my needs. So I'm not 100% sure if the line with the .Zoom = False is necessary, but I assume it is since it was in the code example I found here.)

I don't understand why this code works fine when it's run normally, but gives this message when I'm stepping through it. Any ideas?

 

[Peter_SSs]

I don't know the cause and I cannot reproduce the error but just as a test, what happens if you add this extra line?

.Zoom = 100
.Zoom = False

I think that you do need that .Zoom = False line though

BTW, you could simplify your printarea line. Currently you are taking a range address, referring to that range and then getting the address of that range. That just brings you back to where you started.

<del>.PrintArea = Range(PrintAreaRange).Address</del>
.PrintArea = PrintAreaRange

 

[mcomp72]

I added that line you suggested. When stepping through the code, that line didn't cause any problems. However, when I got to the next line (.Zoom = False), I received the same error as before. Since it works fine when running the code normally, I'll leave it in there, but seems odd that it gives that error message when stepping through.