You are currently offline, waiting for your internet to reconnect

PRJ2000: #ERROR Value in a Cell

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q245863
This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft Project, in the table portion of a task, resource or usage view, you may see an #ERROR value in one or more cells.
This behavior occurs when a custom field contains a value that is either not valid or is greater than its allowable limit.
To work around this behavior, use the appropriate method for your situation.

Method 1: Values Are Greater Than the Maximum Value Allowed

If you use a formula and the #ERROR value is displayed because values are greater than the maximum value allowed in a field, divide the result of the formula to reduce the values of the numbers below the limit.

For example, if you have a formula in the Duration1 field that equals the Duration field multiplied by 35,000, the Duration field equals #ERROR if the value in the Duration1 field is greater than 72,270 days. You can divide the value by a factor, such as 100, to maintain values that are below the maximum of 72,270. You would need to note that the values in this field are 100 times greater than what is displayed. The following is an example of this:

Method 2: Division by Zero

If you use a formula and the #ERROR value is displayed because a function is dividing a value by zero, use the IIF function to display a value that you choose instead of the #ERROR value.

For example, if you have a custom function in the Number1 field that divides cost by actual cost, you receive the #ERROR value when the Actual Cost field equals zero. You can use an IIF function to display zero when the Actual Cost field equals zero, and display the value of cost divided by actual cost when the Actual Cost field is not zero. The following is an example of this:
IIf([Actual Cost]=0,0,[Fixed Cost]\[Actual Cost])
More information
For more information about possible causes and workarounds for the #ERROR message, click Microsoft Project Help on the Help menu, type correct #ERROR conditions in custom fields in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

Article ID: 245863 - Last Review: 12/05/2015 17:27:46 - Revision: 4.0

Microsoft Project 2000 Standard Edition, Microsoft Office Project Professional 2007, Microsoft Office Project Professional 2003, Microsoft Office Project Standard 2007, Microsoft Office Project Standard 2003, Microsoft Project 2002 Standard Edition, Microsoft Project 2002 Professional Edition, Microsoft Project Professional 2010, Microsoft Project Server 2010, Microsoft Project Standard 2010

  • kbnosurvey kbarchive kbpending kbprb KB245863