Visio WBS Chart Wizzard from MS Project 2003 into Visio 2002

[culturecreation]

Hi, can anyone help me with this one please:

When I use the Visio WBS Chart Wizzard it all works well until the
final step and I get an "Organisation Chart Wizzard Error" which says
"Unable to read names from your file".

I use MS Project 2003 Professional and Visio 2002 Professional. I've
installed the latest download fixes from the Microsoft website and even
reinstalled the Visio .... nothing is working. I've searched the
Microsoft website but cannot find a solution to this irritating problem
- I've spent heaps of time trying to work this out ... Help! Thanks ...

 

[d_renny]

Hi,
I have the exact same issue, too bad no one knows the answer.
Let me know if you figured it out, I will subscribe to this thread.
I will certainly post back if I find any information.

 

[Al Edlund]

Since you're using an addin, I would suspect that the tool is calling a
different Project module (i.e. not the one that came with Project 2003 but
rather an earlier version). I've used v2003 with p2003 successfully.
al

 

[d_renny]

Hi Al,
I am using the addin included with project 2003. I will check to see if it
is the correct addin for the version of Visio that I am using - Thanks for
the lead!
I will post back here if this is a solution.

 

[d_renny]

I wanted to add that I am using MS Project Pro 2003 and MS Visio Pro 2002,
both have current service packs. The COM add-in installed in Project is the
one with which it was shipped. The only 2002 WBS Chart Wizzard add-in I
could find in downloads was for Project 2002. Are there known issues with
P2003 and V2002?

 

[d_renny]

Hi I was able to find the answer to this issue.
There is a known, but yet un-posted bug present in the MS Project Pro 2003
SP2 which prevents the WBS Wizard from operating correctly with MS Visio Pro
2002. At the current time, the work-around to this bug is to uninstall MS
Project and then reinstall. Do not install SP2 in order to use the WBS
wizard with MS Visio Pro 2002.
This bug has been reported and confirmed as a submitted issue with MS Support.
I hope that helps!