M
Mitch Powell
I'm having a strange issue with DGET returning #NUM! for a particular
criteria value but not others. The values in the criteria field are as
follows:
Periods: Month & YTD v Budget
Periods: YTD & Year v Budget
Periods: Month, YTD, YTG & Next Yr
Periods: Rolling 12 Months
Periods: Rolling 12 Months plus 2
Periods: Rolling 24 Months
Entities: TIG Consolidated
DGET will successfully return a value when the value in the criteria is ANY
value OTHER than "Periods: Rolling 12 Months". If I use that value in the
criteria it returns #NUM!. It seems to somehow be getting confused due the
presence of another value in the field that is similar ("Periods: Rolling 12
Months plus 2") since if I change the "Periods: Rolling 12 Months plus 2" to
any other value, DGET will successfully return a value using "Periods:
Rolling 12 Months" as the criteria.
I am really stuumped on this one....
criteria value but not others. The values in the criteria field are as
follows:
Periods: Month & YTD v Budget
Periods: YTD & Year v Budget
Periods: Month, YTD, YTG & Next Yr
Periods: Rolling 12 Months
Periods: Rolling 12 Months plus 2
Periods: Rolling 24 Months
Entities: TIG Consolidated
DGET will successfully return a value when the value in the criteria is ANY
value OTHER than "Periods: Rolling 12 Months". If I use that value in the
criteria it returns #NUM!. It seems to somehow be getting confused due the
presence of another value in the field that is similar ("Periods: Rolling 12
Months plus 2") since if I change the "Periods: Rolling 12 Months plus 2" to
any other value, DGET will successfully return a value using "Periods:
Rolling 12 Months" as the criteria.
I am really stuumped on this one....