Microsoft launched SharePoint April 28 SP2 in 2007. At that time, I felt quite ordinary and indifferent. This is also the case. I know that the patch must be better than the patch, but I don't know what problems have been fixed, so I don't have to rush to update it like every time I release the SP patch!
Now let's talk about the problem I encountered. A problem occurs in a document management system under development, where a computing Column cannot be automatically calculated.
The formula for calculating a column is as follows: = text (modification time, "YYYY. MM "). There is no problem in using it elsewhere. If the modification time isThe calculation result is 2009.12. But his value is 1899.12. In the property page, the modification time of the file is indeed 2009-12-04. That is to say, the calculation column does not calculate the modification time. Or the modification time is null. Later, in order to judge the problem, I created another calculation column with the formula = If (isblank (modification time), "null", "non-empty ")
The calculation result is "null", so that it can be concluded that the modification time does not exist when the SharePoint computing column is calculated. This type of problem persists in another SharePoint test environment. It is estimated that this is another SharePoint bug.
A few days later, I found the problem solved when I patch mosssp2 to the test environment.