VBA autofilter on computed table column does not work?

I find that if I use VBA to run an autofilter on a table column of values it works fine, but if I use the same VBA to run an autofilter on the column adjacent to it that has computed values (a formula, no matter how simple, instead of a value, even though the formula displays a numeric value) the filter collapses every single record (row). If I engage the autofilter manually from the spreadsheet on the computed column it works fine - only bad when I run it from VBA.

I am about to put a band-aid on it by running a copy - pastespecial - values on that table's column and running the autofilter on that column, but I think there must be a better way!

Thoughts?

You tell me, here's what I got - olow0s8 is the name of the table.

    olow0s8.Sort.SortFields.Clear
    olow0s8.AutoFilter = False
    With olow0s8.Range
        .AutoFilter Field:=2, _
            Criteria1:="<=" & DateSerial(Year(lDate01), Month(lDate01), Day(lDate01)), Operator:=xlAnd, _
            Criteria2:=">" & DateSerial(Year(lDate02), Month(lDate02), Day(lDate02))

        .AutoFilter Field:=11, Criteria1:=">=" & lLoBal
    End With

The line that is not working is

        .AutoFilter Field:=11, Criteria1:=">=" & lLoBal

If i change the field to 10, obviously immediately adjacent and prior to the errant run column, it filters it perfect.

The only difference between the two is that column 10 has values and column 11 is a SUM of three values.

Just saw your new post come in, about to read-


@skywriter - Will try, need to redact the info...

If I told you I had a tooth pulled yesterday that took an hour and a half to rip out and should stay away from my computer when on meds, will you cut me a little slack?

I am going to shut up now and not post for a couple of days. I found the error. Please pardon me and any trouble I caused...

@FDibbins: In addition to the other one from today, would you be so kind as to make this one disappear?

Thanks Gentlemen-

Dang. I just violated my "not post for a couple days" promise...

Hi, not sure if you managed to get this problem solved, i didnt really plan on looking through all the arguing going on but, there are certain datatypes require you use xlbetween and use < and > together to single out a value and not xlEquals, its something i came across a while back and at the time seemed strange.... but then again most errors seem strange in VBA.......give it a try and let me know.

Thanks
Paul S.

It was a very dumb (hopefully I can write it off to "med influenced") mistake, the second that I made and posted over today, but Thank-you nonetheless!