When I try to print a full month calendar in Outlook 2007, multi-day items
are not wrapping to the next row of the calendar. Instead, they extend off
the right margin and depending on the length, the text isn't visible because
it's centered off the page.

While looking for information about this issue I found another newsgroup
with a thread about the problem: microsoft.public.outlook.calendaring,
http://groups.google.com/group/micro...39b7c566c 7c1

Some people there found that changing the print format to 2 page/month
solved the issue and the items beging to wrap around correctly. I tried this
and it does indeed cause the items to wrap correctly. However, I need to
print a more professional calendar than this solution permits. Splitting the
month in the middle of a page isn't a useful solution for me.

This looks like a bug that effects many people. Has anyone else determined
a solution to this issue or is the Microsoft Office team working on a fix?

Thanks,

Jason

I had the same problem, as a temporary fix I changed it to a recurring
appointment that ended after 2 events. This should work until they fix this
bug

"Jason" wrote:

When I try to print a full month calendar in Outlook 2007, multi-day items
are not wrapping to the next row of the calendar. Instead, they extend off
the right margin and depending on the length, the text isn't visible because
it's centered off the page.

While looking for information about this issue I found another newsgroup
with a thread about the problem: microsoft.public.outlook.calendaring,
http://groups.google.com/group/micro...39b7c566c 7c1

Some people there found that changing the print format to 2 page/month
solved the issue and the items beging to wrap around correctly. I tried this
and it does indeed cause the items to wrap correctly. However, I need to
print a more professional calendar than this solution permits. Splitting the
month in the middle of a page isn't a useful solution for me.

This looks like a bug that effects many people. Has anyone else determined
a solution to this issue or is the Microsoft Office team working on a fix?

Thanks,

Jason