SharePoint List filter with [Null] ?

thinking to find any parameter is available to Filter by empty Field at SharePoint list. But  i found one article , is not with Null….is with nothing to compare mean is null!! ha ha..let me share it at below :

 

http://www.endusersharepoint.com/2009/01/23/filter-by-an-empty-field/

 

I ran into a little quirk this morning that turned out to have an interesting solution. When authors submit articles to the Article Submission Library at EndUserSharePoint.com, there is a date column named “Actual Publication Date” to compare against the “Scheduled Publication Date”.

I want to create a view that shows only the articles that have not been published.

My first pass used the filter section to say “Show items when Actual Publication Date is greater than 1/1/2008″. I figured since it was a date column, any item that had a date in that field would not show up in the view. Nope… didn’t work.

Then I thought “What if you filter for an empty field?” So this time, I set filter to “Show items when Actual Publication date is equal to” and left the value field empty…. Score!!!

Weird one… don’t compare against the date, just leave the filter value empty. You learn something new everyday.

wohoo!! 32bit and 64bit in the SharePoint farm :D

Recently our sharepoint Farm facing out of memory issues when downloading large file. After investigation , analyst on the memory dump we have notice is because of the workload… so our option have 2 , one is upgrade to 64bit sharepoitn farm or add on more web front end server.

suddenly read the article here about performance : http://technet.microsoft.com/en-us/library/cc298550%28office.12%29.aspx

just get to know 32bit and 64bit SharePoint server can mix up :)

Mixing 32-bit and 64-bit servers can affect load balancing. You can run an environment that has some Web servers running the 32-bit version of Office SharePoint Server 2007 and others running the 64-bit version. However, there is a risk that the 32-bit Web servers might become overloaded if the network load balancer is configured to use a less-intelligent model such as round robin. We recommend that you configure the load balancer to manage distribution based on load.

Additionally, deploying both 32-bit and 64-bit servers increases the maintenance overhead for the farm. This is because third-party applications, custom solutions, patches, and software updates for both architectures must be tracked and managed independently

 

the benefit i can think of is we can have less down time to conver our fram from 32 bit to 64 bit by mixing it. :D