my NLS_CALENDAR is PERSIAN and date format is YYYY/MM/DD but when opening datepicker, it don't correct.
i do try find table or object that save Month name of FLOWS_030100 schema, but no success. of course find view that one field is month name but don't change content filed.
However, when you popup the calendar, you're correct - the minimum year supported by the popup calendar is 1920, so it won't properly show today's year (1387) in a Persian calendar. The view WWV_FLOW_YEARS is used by the popup calendar for the year selection list.
Yes - that would be correct. You'll note in my example that the month in the select list is 'فروردین', but the year is not 1387. The minimum year, as derived from the view mentioned above, is 1920.
I don't have a good solution for you to update the available years in the select list, short of changing the underlying view in the FLOWS_xxxxxx schema. In the next release of Application Express, we will replace the calendar popup to overcome design limitations like this. As well, it's our intent to fully support the Persian and Hijra calendars.
>> I don't have a good solution for you to update the available years in the select list, short of changing the underlying view in the FLOWS_xxxxxx schema.
Following Joel’s advice, the following blog entry, by Denes, will help you do just that - http://deneskubicek.blogspot.com/2008/05/limit-datepicker-in-apex.html . For now, it’s the only public solution that allows you control over the years element of the built-in date picker.
I just found out the posted solution works only for the initial load of the datepicker.
Changing the month or year will submit the page and start a new session so the
limitation will not be valid any more. It looks like I will have to pull my blog posting from
the site since it is not correct.
I am sorry for confusing the people. I just didn't test the solution properly. So, until the next
release is here, I see only one solution to the problem - to create your own calendar.
>> Changing the month or year will submit the page and start a new session so the limitation will not be valid any more
In my post I wrote about a “public solution” because I remembered that I played with a JS code which manipulated the date picker (from the time where the buttons were not part of the APEX translation mechanism) but I couldn’t remember why I eventually stopped working on it. Reading your post brought it all back. I encountered the same problem as you. I was able to manipulate the first appearance of the date picker popup window, but every change in the months/years re-displayed it with the original text.
Anyway, it was nice and interesting attempt, on your part, to solve the problems, so I just hope you learned something out of it, and it wasn’t a complete waste of time.
Sure I have learned something out of this situation. But this doesn't mean I give up. Just got
an email from Patrick. He has an iteresting idea which I will try out (by the way, he always
has an idea ;)). Let's see if that is doable. Will post anyway but this time I will test it better
With these setup, I manage to display correct month name and year on calendar. Unfortunately, the day name is incorrect as it show Hijr day name as below:
How do i can get it to display Persian day name on the calendar like below:
The reason why I choose ARABIC language and UTF8 characterset is because Oracle do not yet have the PERSIAN language value supported so far. Is it true?