Code for Project 2000 vs. 2003

[Bob Inwater]

I wrote a VBA applet that runs in MS Word that gathers data from a Word table
and then creates a Project file from that data. It works like a charm with
Word 2002 and Project 2003. Now I need to go backwards and get it to work
with Project 2000. I installed Project 2000 but noticed that there is nothing
in the MSWord references library for the older Project.

Is this because Project 2003 is also still on my box?

Does Project 2000 support this level of integration?

Any thing else I need to know?

 

[JackD]

I would be very surprised if uninstall did NOT remove the library. The easy
way is to assume it does get uninstalled.

 

[JackD]

Answers inline:

--
-Jack ... For Microsoft Project information and macro examples visit
http://masamiki.com/project
or http://zo-d.com/blog/index.html
..

I wrote a VBA applet that runs in MS Word that gathers data from a Word table
and then creates a Project file from that data. It works like a charm with
Word 2002 and Project 2003. Now I need to go backwards and get it to work
with Project 2000. I installed Project 2000 but noticed that there is nothing
in the MSWord references library for the older Project.

Is this because Project 2003 is also still on my box?
Probably

Does Project 2000 support this level of integration?

Yes. Most of the basic methods like adding a task should be unaffected.

Any thing else I need to know?

Read the documentation for Project 2002 VBA and note what is new. Everything
that is not new should be available in Project 2000.

 

[Rod Gill]

When coding for different versions of Project in VBA, the safest way is to
code using early binding (with a referenced library) then unreference the
library and use late binding (Object variables instead of Project objects
etc.

This code then doesn't need a reference and can happily flip from PC to PC.

Or, develop in 2000. When a 2000 macro is opened in a 2003 PC it typically
updates the references to later versions automatically. Open a 2003 macro on
2000 PC and references don't get adjusted.

 

[Bob Inwater]

Thanks guys

When coding for different versions of Project in VBA, the safest way is to
code using early binding (with a referenced library) then unreference the
library and use late binding (Object variables instead of Project objects
etc.

This code then doesn't need a reference and can happily flip from PC to PC.

Or, develop in 2000. When a 2000 macro is opened in a 2003 PC it typically
updates the references to later versions automatically. Open a 2003 macro on
2000 PC and references don't get adjusted.

--

Rod Gill
Project MVP
Visit www.msproject-systems.com for Project Companion Tools and more