I have a column that does not always contain values. If Icreate a filter using Column Is Not Equal To and leave the value empty, the filter works but if I index this column and use the same criteria the records containing a value are not displayed. Is there some type of special syntax that must be used whena column is indexed so that a null/empty strings can be filtered? TIADean

Hi, From what you mentioned above, I have created an indexed column and created a filter using this indexed column, I used the criteria "is not equal to" and left the value empty, it functioned well and filtered the items which the indexed column is null or empty. Could you please provide more details about your problem? Toobtainmore information about indexed column, please refer to: http://office.microsoft.com/en-us/sharepointtechnology/HA101736671033.aspx

I have approximately 12,000 items it the list, after I created the index, the views that use the indexed column are not displaying any items. Other views that do not filter on this column work fine. I removed the index and the view began working again, but it was very slow so I added the index back and now the view returns 0 records. It seems like there is some kind of problem with the indexing process but that is just a guess. Dean

I have a very similar issue. I have an indexed column in a test listthat sometimes has no value. I created a view that shows onlyitems where the column is empty (using "is equal to" and leaving the value empty). This view works just fine until the list has 2000 items. If the list has 1999 items, the view shows the items it should. If the list has 2000+ items, the view is empty. If I change the column so that it is not indexed, the view also shows the items it should.I searched the Knowledge Base, but cannot find any reference to this issue.Mary

We also are having this problem. A list with approximately 2700 items and indexed columns. The views of this list with any type of filtering on the indexed column applied (both thru a filter applied after the view's page is displayed (i.e. vialist headermenu items) or a filter applied via the view's settings page) do NOT work. When the indexed column is removed the filtering works. Thanks to those who posted about this - I was lost as to why this was happening. Can anyone speak to whether this isdue to some configuration setting or a product bug?ThanksRob Roach

Are you having issues filtering on null values or filtering on any values?

I have the same problem.I have a WSS 3 site with an image library with 17,000 images in folders.One column is indexed and has three unique values in it. It is a single line of text.In theAll Itemsview, if I filter by the first value, I get no results. If I filter by the last value, I get no results. If I filter by the middle value, I get the correct result. Remember, these filters are auto-generated by Sharepoint from the data in the list.If I set up a new view with a built-in filter, I get no results (no matter what value I enter).Filtering on non-indexed columns in the same libraryappears to work correctly.I might not have service pack 2. Is this issue fixed in any version?Craig

Have now tried it witha CAML query and get the same result. Inconsistent database maybe? Something is definitely broken in sharepoint anyway.

I am having a similar issue. I did post this in another thread but it seams like this this one may be getting more attention.___I am currently having a similar issue. Simply put, when I remove the "Current = Yes" filter I expect to see all items (current and not). I can see the "Current" field is being set properly when I compare versions of the same item. The latest "Current = Yes" and all other versions "Current = NULL/Empty" are visable when looking at the version history. So why when I remove the "Current" filter do I not see all items. I have also tried to create new lists (both tasks and issues) as tests and neither of those work as well. The task list filter description in settings was even missing the Current is = yes verbage.This sounds like a bug. If there a fix? I tried Nancy's recommendation above and I am still having the same issue.Thanks,greg

Anyone? I remember this working in WSS 2.0. Im currently using MOSS 2007.

I'm getting this as well.... I have 2200 items in my list. It stopped working shortly after I hit 2,000. Turning off indexing on that column fixed the issue for now.

This is still broke in SharePoint 2010... I am suprised that a MVP hasn't replied with some off the way incomplete answer. Where's one of those when you need one?

BUMP

BUMP