Home All Groups Group Topic Archive Search About

Getting Data out of MS Project

Author
29 Aug 2006 2:49 PM
Goofy
Hi,

We have a situation where there is a requirement to extract and report data
to an ASP.NET/VB application from a MSOffice 2003 application.

Best idea to be able to get to the Data ? I know there is a COM Interop
available but have not looked at it yet.

Or any other ideas greatly appreciated

Regards

Author
29 Aug 2006 3:01 PM
Cor Ligthert [MVP]
Goofy,

Why not create your own report or use crystal reports than going to dirty
road.

http://www.vb-tips.com/dbPages.aspx?ID=68888abf-f137-45d1-8a81-e779bfb411c5

Cor

Show quoteHide quote
"Goofy" <m*@mine.com> schreef in bericht
news:u07GOp3yGHA.4796@TK2MSFTNGP06.phx.gbl...
> Hi,
>
> We have a situation where there is a requirement to extract and report
> data to an ASP.NET/VB application from a MSOffice 2003 application.
>
> Best idea to be able to get to the Data ? I know there is a COM Interop
> available but have not looked at it yet.
>
> Or any other ideas greatly appreciated
>
> Regards
>
Author
30 Aug 2006 8:06 AM
Goofy
Thanks for your help

Show quoteHide quote
"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in message
news:eOHvav3yGHA.4732@TK2MSFTNGP03.phx.gbl...
> Goofy,
>
> Why not create your own report or use crystal reports than going to dirty
> road.
>
> http://www.vb-tips.com/dbPages.aspx?ID=68888abf-f137-45d1-8a81-e779bfb411c5
>
> Cor
>
> "Goofy" <m*@mine.com> schreef in bericht
> news:u07GOp3yGHA.4796@TK2MSFTNGP06.phx.gbl...
>> Hi,
>>
>> We have a situation where there is a requirement to extract and report
>> data to an ASP.NET/VB application from a MSOffice 2003 application.
>>
>> Best idea to be able to get to the Data ? I know there is a COM Interop
>> available but have not looked at it yet.
>>
>> Or any other ideas greatly appreciated
>>
>> Regards
>>
>
>
Author
29 Aug 2006 6:22 PM
Oenone
Goofy wrote:
> Best idea to be able to get to the Data ?

If it's MS Project you're reading from, they have an OLE DB database driver
you can use. Lots of information can be found here:

http://www.microsoft.com/technet/prodtechnol/project/project2000/maintain/prjoledb.mspx

I recently used this to write some code to extract all the data from a
project file and store it in a database, and it worked very well.

Some things I found along the way:

1. I couldn't get this to work using ADO.NET. It kept giving me memory
access errors. Instead I dropped back to ADO Classic, and then it worked
fine.

2. The only way to install the driver on a PC appears to be to install the
whole of MS Project. Be aware of the licensing/product activation
implications of this.

3. It appears to be OK to omit the version number from the connection string
(i.e., "Provider=Microsoft.Project.OLEDB; Project Name=..."). This has
worked on every PC I've tried it on, whereas providing a specific version
number obviously requires that specific version of Project to be installed.
Should you wish to provide a version number, the versions appear to be 9 for
Project 2000, 10 for Project 2002 and 11 for Project 2003.

I hope that helps,

--

(O)enone
Author
30 Aug 2006 8:06 AM
Goofy
Thanks for your help


Show quoteHide quote
"Oenone" <oen***@nowhere.com> wrote in message
news:EB%Ig.22451$2w1.9417@newsfe6-gui.ntli.net...
> Goofy wrote:
>> Best idea to be able to get to the Data ?
>
> If it's MS Project you're reading from, they have an OLE DB database
> driver you can use. Lots of information can be found here:
>
> http://www.microsoft.com/technet/prodtechnol/project/project2000/maintain/prjoledb.mspx
>
> I recently used this to write some code to extract all the data from a
> project file and store it in a database, and it worked very well.
>
> Some things I found along the way:
>
> 1. I couldn't get this to work using ADO.NET. It kept giving me memory
> access errors. Instead I dropped back to ADO Classic, and then it worked
> fine.
>
> 2. The only way to install the driver on a PC appears to be to install the
> whole of MS Project. Be aware of the licensing/product activation
> implications of this.
>
> 3. It appears to be OK to omit the version number from the connection
> string (i.e., "Provider=Microsoft.Project.OLEDB; Project Name=..."). This
> has worked on every PC I've tried it on, whereas providing a specific
> version number obviously requires that specific version of Project to be
> installed. Should you wish to provide a version number, the versions
> appear to be 9 for Project 2000, 10 for Project 2002 and 11 for Project
> 2003.
>
> I hope that helps,
>
> --
>
> (O)enone
>