1. If it can be done via Import/Export, then do it there.
2. If it cant, then use Batch.
Data that cant Imported/Exported are the ones in the Dictionaries (e.g., Activity Codes Dictionary, Resource Dictionary, Cost Accoutns Dictionary, etc.)
One great thing about Batch is that you can use it to re-build corrupted P3 files. It works better than the Fix program that ships with P3.
By the way, a Batch Manual can be found in the P3 CD.
Batch is very useful in case you want to build and maintain huge master database (Activity codes, resource directory etc). You need to prepare excel file which can convert data into batch file. But, once done it can save lot of time.
Member for
24 years 3 months
Member for24 years4 months
Submitted by Peter Johnson on Thu, 2002-02-28 06:05
P3batch is a bit fiddly for building up a project - importing wk1 files is easier
P3batch is an excellent and very powerful tool though
We use p3batch a lot in claim evaluation situations where be build up a series of versions of a project at different stages of completion and before and after delay events (this method is called "Time-impact analysis". When the series of projects has been made we use p3 batch to export the same information (completion dates, resource durations etc.) from all of the projects. We have used this for sets of up to 3000 networks with more than 10,000 activities in each network
Member for
24 years 6 months
Member for24 years6 months
Submitted by Tomas Rivera on Tue, 2002-02-26 08:30
I usually deal with schedules between 1,000 and 15,000 activities. I develop all my schedules in Excel and then I import them into P3. ID, activity description and duration are done in Excel. The rest of the information is developed right within P3. Part of this second step is done using Global Change.
Member for
22 years 4 monthsRE: RE: Re: Build you project using p3Batch(utilit
Just one of the points of view out there...
My general rule would be this:
1. If it can be done via Import/Export, then do it there.
2. If it cant, then use Batch.
Data that cant Imported/Exported are the ones in the Dictionaries (e.g., Activity Codes Dictionary, Resource Dictionary, Cost Accoutns Dictionary, etc.)
One great thing about Batch is that you can use it to re-build corrupted P3 files. It works better than the Fix program that ships with P3.
By the way, a Batch Manual can be found in the P3 CD.
Jorge
Member for
22 years 11 monthsRE: Re: Build you project using p3Batch(utility pr
Batch is very useful in case you want to build and maintain huge master database (Activity codes, resource directory etc). You need to prepare excel file which can convert data into batch file. But, once done it can save lot of time.
Member for
24 years 3 monthsRe: Build you project using p3Batch(utility pro...
P3batch is a bit fiddly for building up a project - importing wk1 files is easier
P3batch is an excellent and very powerful tool though
We use p3batch a lot in claim evaluation situations where be build up a series of versions of a project at different stages of completion and before and after delay events (this method is called "Time-impact analysis". When the series of projects has been made we use p3 batch to export the same information (completion dates, resource durations etc.) from all of the projects. We have used this for sets of up to 3000 networks with more than 10,000 activities in each network
Member for
24 years 6 monthsRe: Build you project using p3Batch(utility pro...
I usually deal with schedules between 1,000 and 15,000 activities. I develop all my schedules in Excel and then I import them into P3. ID, activity description and duration are done in Excel. The rest of the information is developed right within P3. Part of this second step is done using Global Change.
Hope this helps