by Michael S. Kaplan, published on 2005/09/28 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2005/09/28/474690.aspx
Back in the end of April I talked a little about the Hijri calendar, and back in the beginning of April I posted some more.
In that last post I talked about the date advance functionality in Regional and Language Options that lets small alterations to the beginning of the month depending on when the moon was spotted, and mentioned that there were plenty of places where the algorithm is supported but the ability to make the changes is not. For example VB/VBA/COM, and also SQL Server.
I was thinking about all of this the other day when I saw this post in Mohamed Sharaf's blog. He was pointing out the best way to treat Hijri dates as dates, and to sort them appropriately. It does deal well with the SQL Server limitations that do not allow dates with years prior to 1753 by assisting with the conversion of the Hijri dates to Gregorian dates.
Now this does not help with the limitation of the date advance setting not being present, but since that setting would only correctly apply to the current month, it is hard to really know how one would apply it. Mohamed's post does deal well with the solvable portion of the limitations in SQL Server related to Hijri dates....
This post brought to you by "۾" (U+06fe, ARABIC SIGN SINDHI POSTPOSITION MEN)
go to newer or older post, or back to index or month or day