Project 2007 on machines with Office 2003 prof.

[Peter.Vreman]

In our environment all the machines has Office 2003 Prof. and has the
Office 2007 Compatability tool kit.
We use, up till now, Project 2000.
We have strong needs for a newer version. From a technical point of
view I would like the users to go to Project 2003 (since we use Office
2003) but they want to go to Project 2007.
To prevent any interference between the two I tried to install only
the Micosoft office Project 2007 components (and not the Office Shared
Features and not the Office Tools).
That ended up not to be acceptable since then they could not use
Macro's.
When I installed the component "Visual Basic for Applications" that
ommision was fixed.
The only thing is now that also in Office 2003 also seems to have a
new VBA.
Before installation it says in Office 2003 macro editor: Microsoft
Visual Basic 6.3 - Version 1024 - VBA: Retail 6.5.1024 Forms3:
11.0.6550
After installation of Project 2007 it says in Office 2003 macro
editor: Microsoft Visual Basic 6.5 - Version 1024 - VBA: Retail
6.5.1024 Forms3: 12.0.4518.101

Now I worry that this might give unexpected problems in Office 2003 or
that there other things overlapping that I haven't seen yet
Is there anyone who can give me some insight on this?

Note 1 - I have to say I had not installed the lateste service packs/
hotfixes when I took the version numbers, off course I plan to do so
when installing it on production systems
Note 2 - We plan to use Project 2007 Standard and Professional

 

[Rod Gill]

A number of people on this group have Project 2007 on Office 2003. As long
as Office 2003 is installed first and any 2007 apps second, there are no
problems that I can remember.

Project 2003 SP3 can read Project 2007 .mpp files.

The only difference between Project 2007 Standard and Pro is that the Pro
version can talk to Project Server 2007 so if you have no intention to buy
Project Server 2007 save yourself the money and buy Standard!

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[Peter.Vreman]

A number of people on this group haveProject 2007onOffice 2003. As long
asOffice 2003is installed first and any 2007 apps second, there are no
problems that I can remember.

Project 2003 SP3 can readProject 2007.mpp files.

The only difference betweenProject 2007Standard and Pro is that the Pro
version can talk to Project Server 2007 so if you have no intention to buy
Project Server 2007 save yourself the money and buy Standard!

Thanks Rob for the quick responce.

But my big worry is the fact that I upgrade the version of VBA and the
forms. And that this might give unexpected behavior in Office2003
Macro's.
Does anyone has any experionce (good or bad) with it, or can anyone
confirm that the new version of the VBA and Forms (and any other
componant that is overwritten) is backwards compatable?

I can make sure that Office2003 is always installed first, since it is
on our base image.

I have office2003 installed in %ProgramFiles%\Microsoft\Office this
result that most of the files will come in %ProgramFiles%\Microsoft
\Office\OFFICE11.
I plan to install Project2007 in the same directory ProgramFiles%
\Microsoft\Office this result that most of the files will come in
%ProgramFiles%\Microsoft\Office\OFFICE12.

 

[Jan De Messemaeker]

Dag Peter,

So far I haven't noticed any problem re backward compatibility.
Mind you if you use automation you may have to adjust Tools, references in
VBA.
HTH


--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

A number of people on this group haveProject 2007onOffice 2003. As long
asOffice 2003is installed first and any 2007 apps second, there are no
problems that I can remember.

Project 2003 SP3 can readProject 2007.mpp files.

The only difference betweenProject 2007Standard and Pro is that the Pro
version can talk to Project Server 2007 so if you have no intention to buy
Project Server 2007 save yourself the money and buy Standard!

Thanks Rob for the quick responce.

But my big worry is the fact that I upgrade the version of VBA and the
forms. And that this might give unexpected behavior in Office2003
Macro's.
Does anyone has any experionce (good or bad) with it, or can anyone
confirm that the new version of the VBA and Forms (and any other
componant that is overwritten) is backwards compatable?

I can make sure that Office2003 is always installed first, since it is
on our base image.

I have office2003 installed in %ProgramFiles%\Microsoft\Office this
result that most of the files will come in %ProgramFiles%\Microsoft
\Office\OFFICE11.
I plan to install Project2007 in the same directory ProgramFiles%
\Microsoft\Office this result that most of the files will come in
%ProgramFiles%\Microsoft\Office\OFFICE12.

 

[Peter.Vreman]

So far I haven't noticed any problem re backward compatibility.

Mind you if you use automation you may have to adjust Tools, references in
VBA.
HTH

Sorry, But I don't understand what is ment with "references in VBA"..

One thing to understand that a lot of the macro's are "Black Boxes"
which users have inhereted from previouse co-workers. So if macro's
has to be changed it might be a risk.

Peter

 

[Jan De Messemaeker]

Hi,

If and when the Project Macros call for Automation (in other words the
macros open Word, Excel...)
In the VB Editor, Tools, References, verify whether the version of the
references towards the office applications are the right ones.
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf