Re: Extracting MSP_TIMEPHASED_DATA via ODBC connection to SQL Server

From: Rod Gill (rodsngtrap_at_hotmail.com)
Date: 07/05/04 

Date: Mon, 5 Jul 2004 19:33:55 +1200

Hi,

I haven't ever finished extracting from the database because I felt the
calendar data needed to be taken into account, so gave up on it and used
other solutions. Either creating a copy of the data or using oledb from .mpp
files, or when using Project Server: using the MSP_VIEW tables.

Why is hourly refresh no good, especially if the schedule is only updated
once a week or less? 

-- 
For VBA posts, please use the public.project.developer group.
For any version of Project use public.project
For any version of Project Server use public. project.server
Rod Gill
Project MVP
For Microsoft Project companion projects, best practices and Project VBA
development services
visit www.projectlearning.com/
"WGHayes" <hayes@nospam99-please.com.au> wrote in message
news:40e8c339$1@duster.adelaide.on.net...
> Rod,
>
> Thanks for the advice, however in my circumstance that approach is not
> workable.  I actually need the data to be dynamically available. (i.e.
cant
> accept overnight or even hourly refresh of data).
>
> You noted that it was a 'pain' to extract the timephased data and make it
> 'accurate' but is it possible?  Have you done this or is this approach a
> 'black hole'?
>
> Thanks,
> WGH.
>
>
> "Rod Gill" <rodsngtrap@hotmail.com> wrote in message
> news:%23wBMeZ0XEHA.2944@TK2MSFTNGP11.phx.gbl...
> > Hi,
> >
> > Firstly I agree that extracting timephased data from the database is a
> pain,
> > especially to make it accurate (to do this I'm sure you need to take
> account
> > of the calendar table as well.
> >
> > Yes the oledb interface is easy.
> >
> > Possible solution: write an application to read daily data from each
> project
> > into a separate database every night. Data won't be right up to date,
but
> > you could provide a utility to re-read individual projects.
> >
> > Your app then reads data straight out of your other database in whatever
> > format is easiest for you.
> >
> > -- 
> > For VBA posts, please use the public.project.developer group.
> > For any version of Project use public.project
> > For any version of Project Server use public. project.server
> >
> > Rod Gill
> > Project MVP
> > For Microsoft Project companion projects, best practices and Project VBA
> > development services
> > visit www.projectlearning.com/
> > "WGHayes" <hayes@nospam99-please.com.au> wrote in message
> > news:40e36f3f$1@duster.adelaide.on.net...
> > > Our requirement is to extract the timephased data from the
> > > MSP_TIMEPHASED_DATA table stored in SQL Server.  After reviewing the
> > > ProjDB.HTM project database tables information and examining the
actual
> > > storage or data in this table it looks like an near impossible job to
> > > extract/interpret the data for a DAY by DAY view.   Has anyone done
> this?
> > >
> > > I have already developed a method to extract the timephased data using
> the
> > > OLEDB provider for MS Project which presents task, assignment and
> resource
> > > views of data at all time levels (i.e. minute, hour, day, etc..)  This
> > works
> > > really well and we have developed a solution that meets our
requirements
> > > perfectly from this data source.  However, this method requires the MS
> > > Project be installed on the Workstation/PC (i.e. the OLEDB provider is
> > > installed by MS Project).  The problem with this is that ALL
> > users(clients)
> > > or our application software will require MS Project to be installed to
> be
> > > able to view this data.  Whilst it is NOT MANDATORY to have MS project
> > > installed to run our software there will be certain aspects of our
> > software
> > > which cannot be used unless MS Project is installed.
> > >
> > > Assistance, comments or advise most welcome.
> > >
> > > Thanks,
> > > WGH.
> > >
> > >
> >
> >
>
>

Relevant Pages
Loading