WSS 3/MOSS 2007 Enterprise We have been using a list view that filters for items where Field1 is blank OR Field2 is blank OR Field3 is blank. These fields are indexed. Suddenly, this view stopped returning rows that certainly meet the criteria. First, we removed the view's filters by selecting Show all items in this view, verified rows were returned, then restored Field1 is blank to the view's filter - still no rows. (Field1 is a simple character field.) Then I tried unindexing the fields, then indexed Field1 only - still no rows. When we filter using the "ad-hoc" method (directly from the list) and filter for "(blanks)", we get the rows we're expecting. This seems to verify that it's not a data problem. Also, tried using SharePoint Designer to build the filter. Verified the CAML is what we expect (creates <IsNull><FieldRef .../></IsNotNull>). Smells like a bug to me, perhaps related to lists that have a significant growth rate. Any ideas? This list is now over 2000 items but performance is good. We take care to index strategic fields like the ones used in this view, etc.

> WSS 3/MOSS 2007 Enterprise Which ?FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.

MOSS 2007 Enterprise (which is running on WSS 3).

Hi, Please try it again and check your event log to see if there are some related errors with detail information. Hope it is helpful!Seven

try creating the same view on any other list and check the results, secondly this might be because of increasing number of items but it should work fine try building the view again with the current fields

Other lists that filter for a blank value return expected results, function properly. Update to the symptoms: We're starting to see more frequent "RENDER FAILED" on this list using other views.

Have you verified that your spaces are special characters? Grab some of the data and paste it into Word and show the characters and see if your space is truely a space. I am 100% sure it is not a bug due to the size of the list. A SharePoint list can hold quite a bit. Shannon Bray - MCT, MCPD, MCTS, MCITP Blog http://shannonbray.wordpress.com User Group Site: http://www.cospug.com

Thanks, Shannon, we have discovered the solution or workaround in this case: One column in the content type was a "Person or Group" which allowed groups. We set that to allow only persons, and the problem symptoms immediately disappeared. (There were no unusual or special characters in the data.)