D
DraNoel
I'm working with an instance of PS 2007 that contains 15 interrelated
projects with (in total) several hundred cross-project task links. I'm
trying to use the Published database to match each "ghost" predecessor/"real"
successor task link in a given project with its corresponding "real"
predecessor/"ghost" successor task link, to
obtain the GUID of the "real" predecessor or successor task that corresponds
to each "ghost" task. There is no obvious way to do this in either the
MSP_LINKS or the MSP_TASKS tables; the MSP_TASKS table has UNIQUEIDENTIFIER
fields named TASK_EXT_TASK_UID and TASK_EXT_PROJ_UID, but those fields are
not populated in either the Draft or Published databases. Please note, I'm
not writing any data to the Project Server databases.
projects with (in total) several hundred cross-project task links. I'm
trying to use the Published database to match each "ghost" predecessor/"real"
successor task link in a given project with its corresponding "real"
predecessor/"ghost" successor task link, to
obtain the GUID of the "real" predecessor or successor task that corresponds
to each "ghost" task. There is no obvious way to do this in either the
MSP_LINKS or the MSP_TASKS tables; the MSP_TASKS table has UNIQUEIDENTIFIER
fields named TASK_EXT_TASK_UID and TASK_EXT_PROJ_UID, but those fields are
not populated in either the Draft or Published databases. Please note, I'm
not writing any data to the Project Server databases.