Printing to A1

[DavidC]

Hi,

I am using Project 2003 normally and notice that when I print out the
network diagram to A1 size (using PDF since I need to have someone else do
the physical print) the last 2 boxes on each page do not have any detail. I
notice also that it is impossible to print preview on PDf when printing to
A1. However at A3 everything works perfectly.

To avoid doubt, it is unlikely an Adobe issue, since if I print using
Project 2007, I can preview fine and the netowrk prints out with all the
detail in the last two boxes on each page.

The reason I work normally in 2003 is that the company is setup fro everyone
else to be on 2003. I have 2007 only since some contractors have upgraded
and I need to read and incorporate their schedules.

Hence the answer is not to only use 2007, I need to be able to work in 2003
and for that to work properly.

Any ideas please.

thanks in advance

DavidC

 

[Mike Glen]

Hi David,

Welcome to the Microsoft Project newsgroup

Please see FAQ Item: 44. Printing Problems

FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm

Hope this helps - please let us know how you get on

Mike Glen
Project MVP

 

[DavidC]

Hi Mike,

On project 2007 there is no problem the network view prints fine. The
problem exists with Project 2003.

Myself and 2 of our IT people have checked everything out and it all pints
to a Project programme issue. The printer is the same when I try printing to
A1 in either project version. We have reinstalled 2003, and reinstalled Adobe
writer.

The deployment of 2003 is enterprise wide using Project 2003 professional,
not standard. For speed reasons I do not work using the server, but work
'offline'.

Project 2007 is not deployed throughout the company yet.

Both versions though are essentially loaded on my computer rather than
acessing through the company ethernet. This allows me to work on site off
line.

So all in all everything we have checked poinmts to an issue with Project
2003 itself.

Regards

DavidC

 

[Dytham]

Hi David;

I have just tried this on my version of Project 2003 SP3 with similar
problems to yours.

Network diagram, PDF print preview to A3 is fine, but with A1 size, last
half dozen boxes on each page are empty. It is even worse at A0 size.

I'm not even using Adobe, but PDF reDirect.

As you say, it does point to being a Project issue.

Rgds,
Chas.

 

[Mike Glen]

Does the Print Preview using A1 or A0 look right before printing? What is
the position if you don't use PDF?


Mike Glen
Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials

 

[DavidC]

For my part, the print preview does not show the A1 size at all. all that I
get is about 3 vertical bands of white with nothing showing. I then take a
punt and print it anyway and that is when I find the last two boxes are
missing the details.

As I mention, it only happens on the 2003 version. The same file opened in
2007 shows properly in print preview and prints out correctly.

Regards

DavidC

 

[Rob Schneider]

Is the solution to rely on 2007 rather than make 2003 work (which
appears not possible)?

 

[DavidC]

No.

I need to work in 2003 as that is the 'rolled out' version at work. I only
have 2007 version so that I can convert schedules from a couple of
contractors who submit them in 2007 version. Yes we can ask for them to
convert, but reality is that it is quicker for me to convert so I can keep up
to date as soon as possible and not waste time going back and forth to get
the conversion done.

DavidC

 

[Rob Schneider]

I know this is cheeky, but if a group in your company takes on the
responsiblity to "rollout" a standard version, then they take on the
responsibility to fix it. They surely have better connections to
Microsoft than this forum has.

 

[DavidC]

Hi Rob,

Understand what you are saying. My guess is that in your part of the world
Microsoft are more customer friendly. My experience and I believe that of
our service people, is that Microsoft have a neat little filtering system
that places all the problems at the feet of the user or want to charge over
$300 for them to research out the problem.

Hence certainly my experience with Microsoft is one that says 'don't bother'
and we have to put up with yet again a faulty piece of microsoft software.

I was hoping that someone else may have found the same problem and knew of a
fix. It was a long shot, which I guess isn't paying off.

Thanks anyway

Regards

DavidC

 

[Rob Schneider]

Naw. I don't anticipate that Microsoft will fix this; nor do I
anticipate that the people/org who "locked" you into Project 2003 will
fix either. On the contrary I *expect* them to since they withhold from
me the ability to fix on my own.

 

[DavidC]

Hi Rob,

Sorry but I don't quite follow. If I buy a product that does not deliver,
then does not the manufacturer have an obligation to fix? I realsie that now
there is project 2007, but that does not detract from the fact that the
original product does not work as designed and expected. If you buy a car
and the electronic ignition does not work properly but the new model does not
have this failign, is the answer now for the manufacturer to simply say
"sorry buy the latest car"?

Sorry but that argument does not work under most consumer legislatio nor any
prudent and responsible manufacturer.

Regards

DavidC

 

[Rob Schneider]

DavidC wrote:

I'm not a product lawyer, but I would think that the obligation would be
spelled out in the purchase agreement. Nothing is warranted for
life--especially software. The Microsoft license agreement has been
perfected over the years and I'm pretty sure they are acting within the
license agreement--that they don't agree to fix all "bugs" all the time
and forever.

I also think that corporate people who lock-down our computers and force
us to use "supported" versions take on an added responsibility to fix
things when things don't work. I "expect" them to do so (for reason
like you say) but I "anticipate" that they a) can't because the vendor
does not, or b) they can't be bothered. b) is unacceptable. a) is a
challenge--but it their challenge as they are the interface with the vendor.

So we agree. Tell the IT people to get Microsoft to fix it. You expect
it. So do I. I just don't anticipate that they will and therefore we
have to pick our battles.

Has your IT department and Microsoft already refused to work this?

 

[DavidC]

Hi Rob,

Whilst product isn't expect to last a lifetime, this is not an issue of
degradation of the product over time, it is a feature that doesn't work and
would not have worked since the beginning, it is just that I havent wanted to
print to A1 before.

Out own IT people have tried to find a solution themselves, I am unsure if
they have approached Microsoft. My earlier comment comes from experience of
trying to deal with Microsoft here where in essence everythi ng is our fault
unless they find otherwise for which they want us to pay $300 first. So in
essence Microsoft here want us to pay them to find a solution for a product
fault. Absolutely bizzare.

Regards

DavidC

 

[Rob Schneider]

Yea, but Microsoft is not *here* (in this newsgroup).