Our software makes use of the Microsoft.Project.OLEDB.9.0 jet provider
installed automatically as part of MSP2000. We have noticed that PC's where
MSP2000 is upgraded to MSP2002 seem to have this provider - i.e. it is not
uninstalled, but PC's with new MSP2002 installations do not have the
provider.

I would have thought that it would not be a breach of the licence agreement
to have both on your PC, as the 2002 licence allows you to run/install
previous versions, just not simultaneously.

I am looking for a quick fix to tide us over while we port the code to
handle either/or Provider. Currently, some of our features are disabled for
MSP2002 users as they do not have the correct provider. Is there a way of
deploying the 2000 provider to 2002 users? (Short of installing the whole of
2000)

Thanks

Regards

Jeff

For Project 2002 there should be a OLEDB.10 provider. Use it. You also get
timephased data for it. See teh PRJOLEDB.HTM file in your Project folders
for details.

--

Visit www.mvps.org/project/ for the Project MVP's FAQ and third party
add-ons

Rod Gill
Microsoft Project MVP
Visit www.projectlearning.com for customized Project and Office VBA macros
and Project companion software

Hi Rod,

Thanks for responding.

This will be the long term solution, we will need to detect for Project 2000
or Project 2002 and choose the provider appropriately - not overly
difficult, but inconvenient. Especially when, for what we wish to achieve,
the 9.0 version has all the features we need; and if we supported any of the
new 10.0 features, we would break compatibility with 2000 users, which some
of our clients still are.
So, it would be great if Project 2002 shipped with an 9.0 OLE provider for
backwards compatibility. Also, if you open a 2000 file in 2002 and save it,
it upgrades all the macro's to reference the Project 10.0 Object Library,
preventing them from working in Project 2000. I understand that this relates
to object model changes, but it would be great if macro's originating from
2000 and left unedited, would keep their references to the previous Object
library when saved. In the current scenario, deploying mpp's with embedded
macro's in our environment (mixed 2000/2002) is overly complicated.

This issue alone rather makes a mockery of Microsoft's claim that MSP 2002
is completely backward compatible. In my view the fact that this feature isn't
supported means it ISN'T fully compatible.

Appreciate your comments on the above.

Thanks

Jeff