What are MPD files for? 1

[migv1]

Greetings:

I've been tasked with creating an Access front end for Project 2003, and I was wondering what file format would be best for database purposes.

I have tried saving a master consolidated project file (created by choosing the third option to create a master project file from all sharer files when opening the shared resource pool) as both MDB and MPD.

With MDB files, if I save the entire project only the task headings (basically the titles of the linked projects, without the datailed tasks) are exported in the MSP_TASKS table. The detailed tasks are saved only if I apply a map to the data export. The downside to doing a manual map of the data is that the resulting MDB file does not restore the proper dependencies and indentions when opened in MS Project.

With MPD files, there is no option to map selected data, so the entire project is always exported.

I would like to save the entire master project, including all the detail tasks from the embedded subprojects.
Is there a procedure for accomplishing this without having to do a manual mapping?

I'm using Project 2003 Standard and Access 2002.
Thanks in advance for any help.

 

[PDQBach]

I have been tasked ..." The first question is WHY?

For the rest of your situation, you will need to understand the underlying object model and database model. Part of this means you'll have to learn about TimePhaseData. Another part of this means that you'll have to learn to understand the linkage between tasks and resources (accomplished via assignments).

How complex is this? Go to Amazon and see how many books there are about the Project object model and data structures. I'll save you some time: what you ask is far too complex to be answered here.

On your installation CDs, look for the file projdb.htm (I think that's it). Good luck.

 

[migv1]

Thanks for the info, PDQBach.

If anything, this should help me explain to my bosses the difficulty involved in what they assumed would be a simple process. They saw that Project files could be saved as MDBs, so the plan was to make a simplified controlled-access front end for users to view and edit their own task data. On a weekly basis, an administrator would then import these changes into Project, enter new subprojects as needed, generate work schedules and assignments, and re-export the updated MDB file to start a new cycle. If only...

I must admit I was in denial for a while and went along with their logic, even though my instincts told me this was trouble the first time I saw the structure of the Project database. (This was thrown my way because I had done some neat things in Access, but I'll be the first to admit that I know next to nothing about Project and its object model.) Our use of Project is limited to tracking of work and facility resources for projects that are typically severely time-constrained. We don't track costs, and we don't even do baselines. I sometimes think we're using a shotgun as a flyswatter, but this situation was inherited from a previous regime, and I'm expected to make it work as efficiently as possible. With these in mind, please consider the following questions from a project management newbie:

1. Are we using the right tool? Or are there other programs out there better suited to simple who-does-what-when?

2. Is the original concept as stated above feasible - are there shops where users use an Access (or other) front end to interact with MS Project?

3. And oh yeah, what is an MPD file used for?

Thanks!

 

[PDQBach]

so the plan was to make a simplified controlled-access front end for users to view and edit their own task data."

Oh, dear god, no, No, NO!!!! The schedule and all information in the schedule is owned by the Project Manager. *NOTHING* gets changed without the PMs approval because changing one thing (say, a user delaying the finish date for a single task) can push everything out while the PM would make that change but restructure the remainder of the plan so that it still hits the target dates.

1. If you need to seriously worry about dependencies then Project is the right tool. But if you're simply tracking against an inflexible schedule, you might find Excel a more appropriate tool. PMI did a survey about 4 years ago asking PMs which tools they were using. By *far* the most popular tool was Excel.

BTW, the "Who Does What When" report from Project is my favourite. By far.

2. I haven't worked in any so I'm not the best person for this. But the biggest use I've read/heard about is to use the MPD files as a way of providing the Project data as input to other systems (rather than, as you appear to want to do, using an Access database as a way of providing a front end to drive data collection in Project).

3. Two things. Well, two that I know of. P98 was renowned for periodically corrupting a file. An oft used "fix" was to save the Project as an MPD file, exit MS Project, restart MS Project, open the MPD file and then save it as an MPP file. The other: to provide a mechanism for people to write reports and to drive information from Project into other systems.