MPX2FIX.EXE version 1.0

Requires VBRUN300.DLL in Windows or Windows/System directory

This utility reads a ".MPX" file produced by Microsoft Project (MSP)
version 3.0 or 4.0, and produces a ".FIX" file that can be
read into Project Manager Workbench for Windows (PMW/w).

These notes are written when PMW/w 1.1.02 was the current version.
Larger projects can be fully converted if using PMW/w 2.0.
(A pre-release version of PMW/w 2.0 was used in testing this.)

In MSP the "export table" should be amended from the default to
include the field "resource list". When the project is saved in
the .MPX format (do not use MPX 1.0) make sure the date format used
is the same as the short date format current in the Windows
Control Panel. That is, the short date format contained in the .MPX file
MUST be one of DMY, MDY or YMD.

Complete dates must be contained in the .MPX file. That is, date formats
such as "Jul 27" are not sufficient for the MPX2FIX utility to use.

Despite a considerable amount of effort, many situations can arise
where the converted file file fails to be read completely by PMW/w.
This is especially true if PMW/w limits are exceeded or approached.
The utility has been successful in converting sizeable MSP projects,
one such plan converted into:
				1       Phase
				290     Activities
				119     Milestones
				1400    Tasks
				575     Dependencies*

This plan was a "live" project and included actual work & status data.
* Using KSMALR to remove dependencies leading INTO completed tasks

If a converted plan fails to be read by PMW/w 1.1.02 then this is suggested:

A. Try to split the MSP project into smaller blocks

or 

B. Run the related KSMALR.EXE utility to reduce the quantity of dependencies
   then retry reading into PMW/w
C. Remove "J" records from the .FIX file (if no actuals are recorded)
   use the related NOJREC.EXE utility, or a text editor to achieve this.
D. Remove all dependency records (K records) and re-try reading into PMW/w
   use the related NOKREC.EXE utility, or a text editor to achieve this.

options B. C. and D. all involve data loss, so adopt only if necessary.

Version notes:

Version 1.0

This version contains user options for:
	Storing Resource Initials, Codes, and Groups
	The task fields; External ID, Category, Short Description, and
	 Deliverable can store ANY field stored in the .MPX file
	 up to the character limits of those fields.
	 (NB Category is always uppercase)
	Dependencies can be converted, or ignored, or minimised
	 by ignoring those dependencies leading INTO completed tasks.

This version will create Phase/Activity/Task/Milestone and Comment records:
	A Phase is created when the MSP record:
		summary = Yes
		outline level=1
		resource list is blank
	An Activity is created when the MSP record:
		summary = Yes
		outline level > 1
		resource list is blank
	A Milestone is created when the MSP record:
		milestone = Yes
		duration <= 1 day
		planned work = 0
		work = 0
		note:   to achieve zero work if resources are assigned
			requires user input in MSP
	A Comment is created when:
		the ID's contained in the MPX file jump numbers

	otherwise the MSP records are treated as TASKS 

This version creates the following record types:
	Project Definition
	Project Description
	Project Calendar        ONLY the first calendar
				 in a .MPX file is used for this
	Resource Definition     ALL resource treated as personnel
				-any cost or quantity resouces require
				 manual adjustment.
				The numeric resource ID is used throughout
				 however resource initials
				 are also stored for reference
	Resource Calendars      ONLY holidays, not patterns
	Task Definition         MANY conditions apply, notably:
				-dates must comply with project calendar
				-end dates must be after start dates
				-is locked IF a constraint date is present
				-is complete if an actual end OR
				 % complete = 100
				-is started if actual start present OR
				 actual work is present, or % complete > 0
				-duration must be at least 2 days IF
				 actual and remaining work exist together
				-refer to .M2F conversion report for
				 information on the adjustments/warnings
	Resource Assignments    contour loading is assumed throughout
	Variable Loadings       these are important if actuals are recorded
	Dependencies            ONLY those from task to task or milestones
				-any dependency involving a summary level is
				 lost see .M2F report file for details
				-ALL SF dependencies in the .MPX are
				 converted into FS and predecessor/successor
				 swapped also


The output of this utility are files with the extension of

	  *.FIX and *.M2F

The *.M2F file is a comprehensive report of conversion conditions, such
as moving dates to comply with the project calendar; duration extensions
when actual and estimate complete would fall on the same day; excluded
dependencies (if any); etc.

Infact Pty. Ltd. (61 3) 614 3166   26th July 1994

The Microsoft Corporation hold copyrights and/or trademarks for:
Microsoft Project
Windows
VBRUN300.DLL

