Using the term "well known" is a matter of opinion. How does it become well known if MS do not inform people ! In NSW, Australia at least, a product with a bug like this classifed as not fit for purpose and normally you would get your maoney back . However we are all involuntary Beta testers in one way or another I suppose
Member for
22 years 9 months
Member for22 years9 months
Submitted by Alexandre Faul… on Fri, 2006-09-01 13:36
Member for
21 years 8 monthsRE: MSP project service pack 2 problems
My reply is to Paul the moderator
Using the term "well known" is a matter of opinion. How does it become well known if MS do not inform people ! In NSW, Australia at least, a product with a bug like this classifed as not fit for purpose and normally you would get your maoney back . However we are all involuntary Beta testers in one way or another I suppose
Member for
22 years 9 monthsRE: MSP project service pack 2 problems
Hello,
This problem only occurs with MS Project 2003 Standard 1st release; it does not exist with ANY other version.
Question is: how did THEY not to check and suppress that enormous bug? As Paul said, this is MSP.
Regards
Member for
24 years 6 monthsRE: MSP project service pack 2 problems
This was a well know problem with early versions of MSP and was fixed with a MSP2003 Hot Fix 832887.
Paul E Harris
Eastwood Harris Pty Ltd, Melbourne, Australia
Planning and Scheduling Training Manual & Book Publishers & Consulting
www.eh.com.au
Member for
19 years 5 monthsRE: MSP project service pack 2 problems
Tom,
Ive heard of this problem on many occasions. Ive yet to use MSP 2003, so have not encountered it personally.
James.