Editing baseline by modifying MSP_TASK_BASELINES does not work

[Chary]

Dear all,
I have the following problem with MS Project 2003 professional.

I wanted to move baseline from one file to another (from old version of file
to new one). So I decided to do the following:

• save both files in MS access format
• Move information from one file to another using MS Access methods

But before even achieving this initial goal, I found the following problem:

When I modify information in MSP_ASSIGNMENT_BASELINES,
MSP_RESOURCE_BASELINES, MSP_TASK_BASELINES it does not have any impact on
what I see, when I open file again in MS Project.

I do the following test:
1) make MS Project file consisting of 1 task, save this task to Baseline1
and then save all file to *.mdb format.

2) Open file in MS Access and modify tables MSP_ASSIGNMENT_BASELINES,
MSP_TASK_BASELINES to start and finish task 1 week later.

3) Then I open it again in MS Project. I see that “Baseline1 start†and
“Baseline1 finish†did not change. So it appears, that MS Project gets this
information from somewhere else.
Furthermore, if I now press Save in MS Project, it puts the start†and
“Baseline1 finish†in MS Access table back where it was before modification.

So, for me these MS Access tables are read only, and MS access keeps
somewhere a copy of original file, which I can’t modify (may be in
RESERVED_BINARY_DATA of table MSP_PROJECTS)

Is there any solution to this?

 

[JulieS]

Hello Chary,

Take a look at the PJDB.HTM file on your computer, particularly the
topic "Setting the flags required to enable updating project data in
the database." I don't believe it's quite as simple as just
modifying the data.

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional
information about Microsoft Project

 

[Chary]

JulieS,

thanks!

It seems to have done the trick, when I followed this rule:

<<
In all cases where project data in a database is edited outside Project, the
column PROJ_EXT_EDITED in the MSP_PROJECTS table must be set to 1.

 

[JulieS]

Superb Chary. Glad you were able to work it out. You're welcome
for the assist and thanks for the feedback.

Julie