In one workbook, I am using the function =EDATE(A1,1), etc to create a list
of months based upon the month entered in cell A1. This formula has worked
for ever on a variety of PCs. However, on one PC I am now getting the #VALUE
error returned, whilst it continues to work on my other PCs.

This implies it is a problem with that particular PC, but I cannot think
what this can be. Does anyone have any ideas as to where I could look.


IanC

On the rogue PC try:-

Tools|addins and load the analysis toolpak.



Mike

"IanC" wrote:

In one workbook, I am using the function =EDATE(A1,1), etc to create a list
of months based upon the month entered in cell A1. This formula has worked
for ever on a variety of PCs. However, on one PC I am now getting the #VALUE
error returned, whilst it continues to work on my other PCs.

This implies it is a problem with that particular PC, but I cannot think
what this can be. Does anyone have any ideas as to where I could look.


IanC

Hi Mike,

I've tried that. I've even tried taking out Analysis Toolpak and then
installing it again, but with no luck. The lack of Analysis Toolpak would
normally give a #NAME error.

It is almost as if this PC thinks there is something wrong with the way the
original date is fomatted, but I have it in as 01/01/2005 which should be
fairly consistent across any format.

IanC

"Mike H" wrote:

On the rogue PC try:-

Tools|addins and load the analysis toolpak.



Mike

"IanC" wrote:

In one workbook, I am using the function =EDATE(A1,1), etc to create a list
of months based upon the month entered in cell A1. This formula has worked
for ever on a variety of PCs. However, on one PC I am now getting the #VALUE
error returned, whilst it continues to work on my other PCs.

This implies it is a problem with that particular PC, but I cannot think
what this can be. Does anyone have any ideas as to where I could look.


IanC

Hi, Ian,

I can replicate the problem by putting a space in front of the date.

Mike

"IanC" wrote:

Hi Mike,

I've tried that. I've even tried taking out Analysis Toolpak and then
installing it again, but with no luck. The lack of Analysis Toolpak would
normally give a #NAME error.

It is almost as if this PC thinks there is something wrong with the way the
original date is fomatted, but I have it in as 01/01/2005 which should be
fairly consistent across any format.

IanC

"Mike H" wrote:

On the rogue PC try:-

Tools|addins and load the analysis toolpak.



Mike

"IanC" wrote:

In one workbook, I am using the function =EDATE(A1,1), etc to create a list
of months based upon the month entered in cell A1. This formula has worked
for ever on a variety of PCs. However, on one PC I am now getting the #VALUE
error returned, whilst it continues to work on my other PCs.

This implies it is a problem with that particular PC, but I cannot think
what this can be. Does anyone have any ideas as to where I could look.


IanC

Hi Mike,

Good idea, but the date seems to be in the correct format (it is displaying
as Jan 2005, which suggests all is OK). However, that has got me thinking
that, for some reason, the offending PC is picking up 01/01/2005 as text as
opposed to a date.


Ian

"Mike H" wrote:

Hi, Ian,

I can replicate the problem by putting a space in front of the date.

Mike

"IanC" wrote:

Hi Mike,

I've tried that. I've even tried taking out Analysis Toolpak and then
installing it again, but with no luck. The lack of Analysis Toolpak would
normally give a #NAME error.

It is almost as if this PC thinks there is something wrong with the way the
original date is fomatted, but I have it in as 01/01/2005 which should be
fairly consistent across any format.

IanC

"Mike H" wrote:

On the rogue PC try:-

Tools|addins and load the analysis toolpak.



Mike

"IanC" wrote:

In one workbook, I am using the function =EDATE(A1,1), etc to create a list
of months based upon the month entered in cell A1. This formula has worked
for ever on a variety of PCs. However, on one PC I am now getting the #VALUE
error returned, whilst it continues to work on my other PCs.

This implies it is a problem with that particular PC, but I cannot think
what this can be. Does anyone have any ideas as to where I could look.


IanC