W
WGHayes
I have project schema loaded into SQL Server and am using automation to load
projects, resources, calendars and to then start MS Project for planning.
In the MSP_PROJECTS table I have created a project with a PROJ_NAME that I
later on wish to change. Using an external app I have updated this field
directly (whilst taking out the necessary locks on the MSP_PROJECTS table -
i.e. PROJ_LOCKED etc..) and all seems to work okay.
I have a problem however in that if that project is linked to a central
RESOURCE POOL then the details in the pool are not updated/refreshed. The
result is that the POOL now contains a reference to the OLD project and the
NEW project name even though only one project and one set of
tasks/assignments exist.
I have tried de-linking from resource pool prior to changing PROJ_NAME and
then re-linking after however this still duplicates. I cannot see anywhere
in the MSP projects schema in SQL where the resource pool is keeping this
OLD project name reference. Does anyone have any suggestions?
Thanks.
WGH
projects, resources, calendars and to then start MS Project for planning.
In the MSP_PROJECTS table I have created a project with a PROJ_NAME that I
later on wish to change. Using an external app I have updated this field
directly (whilst taking out the necessary locks on the MSP_PROJECTS table -
i.e. PROJ_LOCKED etc..) and all seems to work okay.
I have a problem however in that if that project is linked to a central
RESOURCE POOL then the details in the pool are not updated/refreshed. The
result is that the POOL now contains a reference to the OLD project and the
NEW project name even though only one project and one set of
tasks/assignments exist.
I have tried de-linking from resource pool prior to changing PROJ_NAME and
then re-linking after however this still duplicates. I cannot see anywhere
in the MSP projects schema in SQL where the resource pool is keeping this
OLD project name reference. Does anyone have any suggestions?
Thanks.
WGH