Workbooks were originally written in 2003 and are on a network - users work
via TS. Currently in middle of migration, so some users are opening in 2007
as a 2003 compatible file. Seems to be an intermittent problem, sometimes
the XIRR and EDATE functions seem to be OK, othertimes they are replaced by
#N/A.

It is not the case that formula refers to a cell that uses the NA()
function or to a UDF that returns the xlErrNA value.

Currently using Service Pack 1 and operating via Terminal Services.

Thanks
"JoeU2004" wrote:

"Wibbs" wrote:
XIRR and EDATE functions are sometimes changed to #NA in 2007
when saved in compatability mode.

Please clarify the problem statement.

First, do you mean that the problem is seen when the workbook is opened in
Excel 2007? Or do you mean when it is opened in Excel 2003?

Also, is it opened on the same computer, or on a different computer? Is the
file on a shared disk and opened over the network?

Second, do you mean the #N/A error or the #NAME? error?

The #NAME? error suggests that the ATP has not been enabled ("loaded").
Note that the ATP can be installed, but not enabled. See Tools Add-Ins in
Excel 2003.

The #N/A error indicates that a formula refers to a cell that uses the NA()
function or to a UDF that returns the xlErrNA value. Since these are
programmable errors, you need to look at the worksheet and macro designs to
understand the conditions when these errors are returned. The Evaluate
Formula feature might help. See Tools Formula Auditing in Excel 2003.


----- original message -----

"Wibbs" wrote in message
...
XIRR and EDATE functions are sometimes changed to #NA in 2007 when saved
in
compatability mode. This does not happen everytime, but has happened to a
number of spreadsheets. These provide crucial information to the company
and
would like to know how to fix this.