DCOUNTA and #NAME? errors

Posted by tee on July 17, 2001 10:20 PM

Hi Everyone

I have a DCOUNTA criteria set up and I have just changed one date to 01/01/2002 from 01/01/2001. Now I have this error message. I have not changed any other values and names.

January Date Date VSU_No Client Field : Client
01/01/02>=1/1/02#NAME? Count : 0

1st Date field is
=">="&TEXT(DATE(YEAR(AP20),MONTH(AP20),1),"d/m/yy")
2nd Date field is
="&LT;="&TEXT(EOMONTH(AP20,0),"d/m/yy")
It is the 2nd date field that keeps bringing up the Name error.

Any idea what the problem is????

Thanks in advance
Tee

Posted by Aladin Akyurek on July 17, 2001 10:32 PM

Tee,

It could be EOMONTH that leads to the #NAME? error. You need to install Analysis Toolpak via the option Tools|Add-ins.

Aladin

Posted by tee on July 17, 2001 10:55 PM

Found the solution

Hi Everyone I found this solution and it works - thanks to Kevin.

Re: Excel Name Problem
Kevin Rabenaldt 11/20/00 10:59 a.m.

Over the weekend the solution was found by my brother. My formulas contain named cells and also sometimes has a function called EOMONTH. EOMONTH is part of the "Analysis Toolpak". This can be added by going to Tool, then to Add-ins. Check the box for Analysis ToolPak and Analysis ToolPak VBA. Once that was done the spreadsheet worked correctly. The the common reason for ?name# is name that is not defined. I thought it was a named cell but in reality, Excel did not recognize EOMONTH because Analysis ToolPak was not installed.

Thanks, and I hope this helps someone in the future.

Kevin

Posted by tee on July 17, 2001 10:58 PM

Many thanks just found it.

Posted by Aladin Akyurek on July 18, 2001 12:09 AM

Re: Found the solution

If you don't have any VBA code for this particular workbook, better uncheck Analysis Toolpak VBA.

Aladin I found this solution and it works - thanks to Kevin.