M
Mark
Hi Folks
Using Project Professional 2002.
A little background info...
We have a (MS Access based) cost control program from which we want to write
new tasks to an MS Project file saved as an MDB. Basically, the cost control
software is used for estimating modules of a large project. The modules
relate to various phases etc. and the phase dates, along with estimate and
purchasing information, allow us to do cost forecasting. The modules are
(will be) exported to Project as tasks. Phase dates and dependancies are to
be managed in Project (periodically being read back to the cost app), whilst
cost information and progress are extracted from the cost app and updated to
the Project file. Progress being based entirely on hours burned.
The problem...
I'm writing new tasks to the MDB using SQL strings in VBA, setting the
relevant ext_edit flags etc. but am having problems in relation to
percentage complete, dates and durations. Project is set for 8 hours a day,
20 days per month btw.
My questions are then, given a start date, end date and percentage hours
burned:
a) Can I prevent project changing the start and end dates (it seems to
default to the nearest week day ignoring weekends)? (Not necessarilly too
important)
b) What duration and date fields do I need to update in order for the
percentage complete to reflect our hours burned?
c) What is the most reliable way to calculate durations? I am experimenting
with using something like:
dur=(datediff("d",startDate, endDate)+1)-(datediff("w",startDate,
endDate)*2) *4800
to get rid of weekends...
d) Where does 4800 come from in respect to duration (a one day task shows
4800 in the TASK_DUR field)?
e) Does any one have a link to some field definitions / usage descriptions
for MSP_TASKS?
Many thanks
Mark
Using Project Professional 2002.
A little background info...
We have a (MS Access based) cost control program from which we want to write
new tasks to an MS Project file saved as an MDB. Basically, the cost control
software is used for estimating modules of a large project. The modules
relate to various phases etc. and the phase dates, along with estimate and
purchasing information, allow us to do cost forecasting. The modules are
(will be) exported to Project as tasks. Phase dates and dependancies are to
be managed in Project (periodically being read back to the cost app), whilst
cost information and progress are extracted from the cost app and updated to
the Project file. Progress being based entirely on hours burned.
The problem...
I'm writing new tasks to the MDB using SQL strings in VBA, setting the
relevant ext_edit flags etc. but am having problems in relation to
percentage complete, dates and durations. Project is set for 8 hours a day,
20 days per month btw.
My questions are then, given a start date, end date and percentage hours
burned:
a) Can I prevent project changing the start and end dates (it seems to
default to the nearest week day ignoring weekends)? (Not necessarilly too
important)
b) What duration and date fields do I need to update in order for the
percentage complete to reflect our hours burned?
c) What is the most reliable way to calculate durations? I am experimenting
with using something like:
dur=(datediff("d",startDate, endDate)+1)-(datediff("w",startDate,
endDate)*2) *4800
to get rid of weekends...
d) Where does 4800 come from in respect to duration (a one day task shows
4800 in the TASK_DUR field)?
e) Does any one have a link to some field definitions / usage descriptions
for MSP_TASKS?
Many thanks
Mark