H
Hannah
Hi there
Ive written a series of stored procedures in SQLServer 2000 to insert
a new project into the MSProject 2000 database (the projects are
fairly simple and only contain tasks,assignments and resources).
In the same stored procedure, the project is added to a pre-created
msproject,
the idea being that all the projects can be managed from one main
project, as sub-projects.
However, what seems to be happening is that while the projects are
being created fine as sub projects, (I can see them all in the parent
project no problem) when I try and save any changes while they are
being viewed as sub projects, none of the changes stick. On re-opening
the main project, none of the changes to the sub projects have stuck.
I have narrowed the reason down to the fact that the ext_edit_ref_data
field in
the MSP_resources and MSP_assignments MSProject tables for the
relevent sub project are not updated when the project is saved as a
sub project.
On creating the projects, the ext_edit_ref_data field is set to '1',
as is required for the creation of new assignments / resources outside
of the MSProject application. This is the same for the MSP_Tasks
table, which
seemingly bizarrely IS being reset to NULL once it is saved in the
subproject.
?!?! Ive got the projdb.htm documentation, and although helpful for
the rest of my work, it hasnt help me with this problem. Hence me
posting here.
Can anyone help me out and perhaps suggest anything i should be
looking to do to enable saving to stick in the sub projects. I dont
understand why MSProject isnt setting the ext_edit_ref_data to null
for the assignments and resources tables. Am I missing something?
Incidently, when I open up the sub projects individually (i.e. in
their own MSproject application) and save the changes, all is well,
and any changes made to the project (regardless of whether it is as a
sub project or not) from that point on are fine (when i checked the DB
- the ext_edit_ref_data field in the msp_assignments and msp_resources
has been reset to null).
I dont really want to have to open up the projects inidivually though,
just so that changes can be saved when the project is viewed as a sub
project.
Any help is gratefully appreciated.
Regards,
Hannah
Ive written a series of stored procedures in SQLServer 2000 to insert
a new project into the MSProject 2000 database (the projects are
fairly simple and only contain tasks,assignments and resources).
In the same stored procedure, the project is added to a pre-created
msproject,
the idea being that all the projects can be managed from one main
project, as sub-projects.
However, what seems to be happening is that while the projects are
being created fine as sub projects, (I can see them all in the parent
project no problem) when I try and save any changes while they are
being viewed as sub projects, none of the changes stick. On re-opening
the main project, none of the changes to the sub projects have stuck.
I have narrowed the reason down to the fact that the ext_edit_ref_data
field in
the MSP_resources and MSP_assignments MSProject tables for the
relevent sub project are not updated when the project is saved as a
sub project.
On creating the projects, the ext_edit_ref_data field is set to '1',
as is required for the creation of new assignments / resources outside
of the MSProject application. This is the same for the MSP_Tasks
table, which
seemingly bizarrely IS being reset to NULL once it is saved in the
subproject.
?!?! Ive got the projdb.htm documentation, and although helpful for
the rest of my work, it hasnt help me with this problem. Hence me
posting here.
Can anyone help me out and perhaps suggest anything i should be
looking to do to enable saving to stick in the sub projects. I dont
understand why MSProject isnt setting the ext_edit_ref_data to null
for the assignments and resources tables. Am I missing something?
Incidently, when I open up the sub projects individually (i.e. in
their own MSproject application) and save the changes, all is well,
and any changes made to the project (regardless of whether it is as a
sub project or not) from that point on are fine (when i checked the DB
- the ext_edit_ref_data field in the msp_assignments and msp_resources
has been reset to null).
I dont really want to have to open up the projects inidivually though,
just so that changes can be saved when the project is viewed as a sub
project.
Any help is gratefully appreciated.
Regards,
Hannah