Appendix B: Field Reference


Overview

This appendix lists all the fields available in Microsoft Office Project 2003, broken down by type of data:

  • Currency

  • Date

  • Duration

  • Enumerated

  • Indicator

  • Integer

  • Outline Code

  • Percentage and Number

  • Text

  • Yes/No (Boolean)

In addition, the following special categories of fields are grouped together for your reference toward the end of this appendix:

  • Custom

  • Earned Value

  • PERT Analysis

Each row in the following tables contains the name of a field in Project 2003 and the category in Microsoft Project to which the field belongs; for example, tasks , resources, and so on. Each row contains a description of the field and the name of the field when it's exposed using the Microsoft Office Project 11.0 OLE DB Provider. Each row also includes the name of the field when you open a project as a database, for example, when you save a project as a Microsoft Office Access database and open it in Access.

Fields are listed in this appendix if the field in the database contains the same data entered or added through Microsoft Project. Some fields listed in this appendix that can be accessed using the Project 11.0 OLE DB Provider do not have a corresponding field in the Microsoft Project database. These "missing" fields are actually the results of calculations based on values stored in other fields. For example, the Cost Variance field contains the difference between a baseline cost and total scheduled cost. The Cost Variance field can be assigned in Microsoft Project and exposed using the OLE DB Provider, but it doesn't have its own field in the Microsoft Project database because Cost Variance is the result of a calculation (Cost “ Baseline Cost).

Most fields in Microsoft Project can be found in the following OLE DB Provider or Microsoft Project database tables:

  • Assignment.       Fields are stored in the Assignments table in OLE DB and in the MSP_ASSIGNMENTS table in the Project database.

  • Assignment (Timephased).       Fields are stored in the Minute, Hour, Day, Week, and Month assignment-timephased tables in OLE DB.

  • Resource.       Fields are stored in the Resources table in OLE DB and in the MSP_RESOURCES table in the Microsoft Project database.

  • Resource (Timephased).       Fields are stored in the Minute, Hour, Day, Week, and Month resource-timephased tables in OLE DB.

  • Task.       Fields are stored in the Tasks table in OLE DB and in the MSP_TASKS table in the Microsoft Project database.

  • Task (Timephased).       Fields are stored in the Minute, Hour, Day, Week, and Month task-timephased tables in OLE DB.

  • Custom.       Fields are stored in the tables they are associated with in OLE DB; for example, custom assignment cost fields are in the Assignments table.

start sidebar
Custom Fields in the MSP_PROJECTS Database

Although custom fields are stored in the OLE DB Provider tables, custom fields are stored in the following tables in the MSP_PROJECTS database:

  • MSP_ASSIGNMENT_BASELINES

  • MSP_DATE_FIELDS

  • MSP_DURATION_FIELDS

  • MSP_FLAG_FIELDS

  • MSP_NUMBER_FIELDS

  • MSP_OUTLINE_CODES

  • MSP_RESOURCE_BASELINES

  • MSP_TASK_BASELINES

  • MSP_TEXT_FIELDS

Data stored in the MSP_PROJECTS database tables aren't as easy to use as the custom fields in the OLE DB Provider because custom fields in the Project database are defined by multiple fields; and the tables can contain data for assignments, resources, and tasks.

If you're set up for enterprise project management using Microsoft Office Project Professional 2003 and Microsoft Office Project Server 2003, you have access to enterprise resource multivalue fields. As its name implies, these multivalue fields can contain multiple values and are stored in the MSP_MV_FIELDS table in the Microsoft Project database.

end sidebar
 
Note  

Each of the five timephased tables for assignments, resources, and tasks are named n TimephasedBy X where n is assignments, resources, or tasks; and X is Minute, Hour, Day, Week, or Month.

Cross-References  

For more information about working with fields and adding them to tables, see "Using Tables" and "Using Fields" on page 04xx. For more information about custom fields, see "Customizing Fields" and "Working with Outline Codes".

Cross-References  

For detailed information about each individual field, including calculations, best uses, and examples, refer to the Fields Reference section of Project Help. To do this, click Help, Microsoft Project Help. Click Table Of Contents and then click Reference. Click Fields Reference, click Table Of Contents, and then click Reference. Click Fields Reference.

Cross-References  

For more information about the OLE DB provider tables and the Project database tables, the fields in these tables, and how to understand the data in these tables and how it links to assignments, resources, or tasks, see Pjdb.htm ”included on the Microsoft Office Project Standard 2003 or Project Professional 2003 installation CD.




Microsoft Office Project 2003 Inside Out
Microsoft Office Project 2003 Inside Out
ISBN: 0735619581
EAN: 2147483647
Year: 2003
Pages: 268

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net