having the same problem!!!!!!!!


"Sally" wrote:

Still no fix for this very annoying problem (the word wrap)?

"Kremmen" wrote:

Thanks Nick

Yes that's the error, at least it's not only me. I wonder why no-one else
has spotted this ?????

Krem

"Nick B" wrote:

I take that back, I just encountered it... If in the print dialog you change
the date range and click "preview", it will stop responding. Damn it
Microsoft.

"Nick B" wrote:

Unfortunately I don't seem to be getting that hang, unless I'm not doing the
right thing to get it to hang.

"Kremmen" wrote:



"Nick B" wrote:

I should clarify that I've only noticed the last problem, multi-week
events not wrapping around to subsequent weeks. Interestingly, it does leave
a space for the event on other days containing events, but the multi-week
event box itself just extends to the edge of the printed page. The MDI file
demonstrating this can be obtained he
http://abacus.bates.edu/~nbauer/Outl...onthlyWrap.mdi

"Nick B" wrote:

I just got the Trial version, which should be identical to the full version,
and it exhibits this behavior too. How could such a bug get through to RTM?

"Kremmen" wrote:

I have just installed the MSDN version of Outlook 2007.

When I try to print the Monthly calendar it works if I leave the default
dates alone but it hangs if I change the 'date range'.

Also hangs in print preview if I change the date range there as well.

Also got the problem with events spanning several weeks not wrapping around
on to subsequent weeks.

Yes, that's the problem, how on earth did that not get picked up ?

Do you also get teh problem with a hang if you change the 'print range' via
the print dialog ?

It seems that someone from MS (Sue Mosher, Milly Staples, Judy Gleeson) would
at least aknowledge this rather big defect. Just letting us know that someone
is working on the problem would ease my mind.

"tjfcopp" wrote:

having the same problem!!!!!!!!


"Sally" wrote:

Still no fix for this very annoying problem (the word wrap)?

"Kremmen" wrote:

Thanks Nick

Yes that's the error, at least it's not only me. I wonder why no-one else
has spotted this ?????

Krem

"Nick B" wrote:

I take that back, I just encountered it... If in the print dialog you change
the date range and click "preview", it will stop responding. Damn it
Microsoft.

"Nick B" wrote:

Unfortunately I don't seem to be getting that hang, unless I'm not doing the
right thing to get it to hang.

"Kremmen" wrote:



"Nick B" wrote:

I should clarify that I've only noticed the last problem, multi-week
events not wrapping around to subsequent weeks. Interestingly, it does leave
a space for the event on other days containing events, but the multi-week
event box itself just extends to the edge of the printed page. The MDI file
demonstrating this can be obtained he
http://abacus.bates.edu/~nbauer/Outl...onthlyWrap.mdi

"Nick B" wrote:

I just got the Trial version, which should be identical to the full version,
and it exhibits this behavior too. How could such a bug get through to RTM?

"Kremmen" wrote:

I have just installed the MSDN version of Outlook 2007.

When I try to print the Monthly calendar it works if I leave the default
dates alone but it hangs if I change the 'date range'.

Also hangs in print preview if I change the date range there as well.

Also got the problem with events spanning several weeks not wrapping around
on to subsequent weeks.

Yes, that's the problem, how on earth did that not get picked up ?

Do you also get teh problem with a hang if you change the 'print range' via
the print dialog ?

None of the MVP's work for MS, we're all volunteers. For the most part your
guess is as good as ours is about what they're working on, or even what they
plan to fix.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Sally" wrote in message
...
It seems that someone from MS (Sue Mosher, Milly Staples, Judy Gleeson)
would
at least aknowledge this rather big defect. Just letting us know that
someone
is working on the problem would ease my mind.

I appreciate the enlightenment. So MS may not even be monitoring these
exchanges or be aware of the problems. That's pretty profound.

Are you aware of this problem? Do you have Outlook 2007?

"Ken Slovak - [MVP - Outlook]" wrote:

None of the MVP's work for MS, we're all volunteers. For the most part your
guess is as good as ours is about what they're working on, or even what they
plan to fix.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Sally" wrote in message
...
It seems that someone from MS (Sue Mosher, Milly Staples, Judy Gleeson)
would
at least aknowledge this rather big defect. Just letting us know that
someone
is working on the problem would ease my mind.

These newsgroups are all peer to peer. There's no MS presence in them for
the most part.

As we find bugs or notice posts about bugs we try to report them to MS but
they don't even have a formal mechanism for that set up, so it's rather hit
or miss.

I have Outlook 2007 but I never use Outlook to print so I'm not familiar
with that specific problem. There are a lot of calendar related printing
problems though. The only official way to notify MS about a problem like
this would be to open a support incident. If it's a bug then you wouldn't be
charged for the support incident.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Sally" wrote in message
news
I appreciate the enlightenment. So MS may not even be monitoring these
exchanges or be aware of the problems. That's pretty profound.

Are you aware of this problem? Do you have Outlook 2007?

i create a incident report and here's MS's response:

Thanks for the update. I have tested both of your setup and found that it
works in BETA but not in the Final release. Currently it looks to be a
changed in the final release that is causing this issue. I am currently
working with the Dev team to try and find out what could be the cause. I will
keep you updated on the issue as soon as I get some more information.


the problem is in the final relaease code. the Beta code works fine


"Ken Slovak - [MVP - Outlook]" wrote:

These newsgroups are all peer to peer. There's no MS presence in them for
the most part.

As we find bugs or notice posts about bugs we try to report them to MS but
they don't even have a formal mechanism for that set up, so it's rather hit
or miss.

I have Outlook 2007 but I never use Outlook to print so I'm not familiar
with that specific problem. There are a lot of calendar related printing
problems though. The only official way to notify MS about a problem like
this would be to open a support incident. If it's a bug then you wouldn't be
charged for the support incident.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Sally" wrote in message
news
I appreciate the enlightenment. So MS may not even be monitoring these
exchanges or be aware of the problems. That's pretty profound.

Are you aware of this problem? Do you have Outlook 2007?

So they're acknowledging a problem in the release code? It's not the first
that wasn't there in the beta. At least it's on their radar now, if it
wasn't before.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"tjfcopp" wrote in message
...
i create a incident report and here's MS's response:

Thanks for the update. I have tested both of your setup and found that it
works in BETA but not in the Final release. Currently it looks to be a
changed in the final release that is causing this issue. I am currently
working with the Dev team to try and find out what could be the cause. I
will
keep you updated on the issue as soon as I get some more information.


the problem is in the final relaease code. the Beta code works fine