I have a VB2005 (frontloader) which automates Excel (creates new
instance, new file etc). I have put a datepicker on the frontloader
but when the date gets put into the Excel file I get a #NAME error on
five cells that are dependent on the cell the date has been placed
into. These file cells use the EOMONTH and EDATE functions.

Not sure if it is to do with the the value in the cell not being a
date as such. I'm using the DateSerial(y,m,d) in the frontloader to
populate the cell.

Please anyone help?

Thanks

Meldrum

#Name is another way of saying "Formula not found". So your vb app is not in
play and is probably working fine.

Not suggesting that you rtfm or anything, but to quote Excel help... :)

EOMONTH

[See Also]

Returns the serial number for the last day of the month that is the
indicated number of months before or after start_date. Use EOMONTH to
calculate maturity dates or due dates that fall on the last day of the month.

If this function is not available, and returns the #NAME? error, install and
load the Analysis ToolPak add-in.

....

Hope that helps!



"meldrum_scotland" wrote:

I have a VB2005 (frontloader) which automates Excel (creates new
instance, new file etc). I have put a datepicker on the frontloader
but when the date gets put into the Excel file I get a #NAME error on
five cells that are dependent on the cell the date has been placed
into. These file cells use the EOMONTH and EDATE functions.

Not sure if it is to do with the the value in the cell not being a
date as such. I'm using the DateSerial(y,m,d) in the frontloader to
populate the cell.

Please anyone help?

Thanks

Meldrum