Prev: Chart datalabels linked to cells
Next: Modify code from paste values to change font color / multiple
From: Ayo on 9 Mar 2010 14:16 errorWS.Range("B3").Value = Application.WorksheetFunction.CountA("A5:A" & errorWS_startRow - 1) The above line of code is always 1, even when errorWS_startRow is much > 1, i.e: errorWS_startRow=144, 749 etc. Any ideas what is going on?
From: ker_01 on 9 Mar 2010 14:51 I'd suggest including the sheet reference for the CountA; something like this (untested) errorWS.Range("B3").Value = Application.WorksheetFunction.CountA(errorWS.Range("A5:A" & errorWS_startRow - 1)) "Ayo" wrote: > errorWS.Range("B3").Value = Application.WorksheetFunction.CountA("A5:A" & > errorWS_startRow - 1) > > The above line of code is always 1, even when errorWS_startRow is much > 1, > i.e: > errorWS_startRow=144, 749 etc. > > Any ideas what is going on?
From: JLGWhiz on 9 Mar 2010 14:55
If the cells from A5 to A & errorWS_startRow-1 are empty, you will get either 1 or zero depending on whether there is data in the startRow - 1 or not. CountA only counts cells with data that has a value. It will not count empty cells but does count cells with zero, "" or ' characters that are hidden because they have values. So, the range you are testing must be empty except for one cell. "Ayo" <Ayo(a)discussions.microsoft.com> wrote in message news:601B0838-D550-4E26-8859-C9B2335254FD(a)microsoft.com... > errorWS.Range("B3").Value = Application.WorksheetFunction.CountA("A5:A" & > errorWS_startRow - 1) > > The above line of code is always 1, even when errorWS_startRow is much > > 1, > i.e: > errorWS_startRow=144, 749 etc. > > Any ideas what is going on? |