From: OldTimer on
I'm using Word 2003 on XP SP2 Home Edition to print a 12 page booklet (half
page of 8.5 X 11).

While trying to overcome problems with printing correct page sequencing. I
ran across Microsoft KB 286856 which states that Microsoft acknowledges a
problem in Word 2003 when using Manual duplex.

I find it incredulous (wow, I haven't had to use that word for quite a
while), that Microsoft would confirm the problem and just leave it at that -
with no suggested work around. Or is there one?
From: OldTimer on
I forgot to mention that the link (in Suzanne Barnhill's article on Booklet
Printing) in the section 'Word 2002 and above . . . ' which reads: "allows
you to create a booklet within Word itself" doesn't work for me. Is there a
work around in it, perhaps?

"OldTimer" wrote:

> I'm using Word 2003 on XP SP2 Home Edition to print a 12 page booklet (half
> page of 8.5 X 11).
>
> While trying to overcome problems with printing correct page sequencing. I
> ran across Microsoft KB 286856 which states that Microsoft acknowledges a
> problem in Word 2003 when using Manual duplex.
>
> I find it incredulous (wow, I haven't had to use that word for quite a
> while), that Microsoft would confirm the problem and just leave it at that -
> with no suggested work around. Or is there one?
From: Suzanne S. Barnhill on
> I find it incredulous (wow, I haven't had to use that word for quite a
> while)

No, you're incredulous; it's incredible.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
http://word.mvps.org

"OldTimer" <OldTimer(a)discussions.microsoft.com> wrote in message
news:182AACAC-3BC9-4BD1-B07C-29F6CEA0F6E1(a)microsoft.com...
> I'm using Word 2003 on XP SP2 Home Edition to print a 12 page booklet
> (half
> page of 8.5 X 11).
>
> While trying to overcome problems with printing correct page sequencing.
> I
> ran across Microsoft KB 286856 which states that Microsoft acknowledges a
> problem in Word 2003 when using Manual duplex.
>
> I find it incredulous (wow, I haven't had to use that word for quite a
> while), that Microsoft would confirm the problem and just leave it at
> that -
> with no suggested work around. Or is there one?
>