Wibbs said:
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.
That is much clearer. One detail remains unclear to me: who is seeing the
intermittent #N/A error: the Excel 2007 user or the Excel 2003 user?
Have you observed this "intermittent" behavior yourself, or are people
simply reporting it to you?
Meaning no disrespect, but in my experience, most of the time that customer
report "intermittent" behavior, it is really because circumstances changed;
for example, they changed the values of some parameters.
Since the users are using Terminal Services to access the file and/or Excel,
we can rule out the network as a source of intermittent behavior. All the
processing is taking place on the central computer.
I am not aware of any circumstances where XIRR and EDATE might return the
#N/A error, at least not according to Excel 2003 documentation. Does the
Excel 2007 Help pages indicate any circumstances when that might happen?
I see that this problem has been reported and discussed several times since
2007. I have not found any resolution of the problem.
However, in one case, forcing recalculation remedied the error
(ctrl-alt-F9).
----- original message -----